Database Develop

Phone Stuck In Recovery

Hi guys. I somehow messed things up really bad.
I was running a modded ROM, but decided I wanted to go back to unrooted stock. I followed this instructions in this video: https://www.youtube.com/watch?v=6avEPGWB8E0
Unfortunately, things didn't work out. When I tried flashing the files it kept saying "system not found". Now I'm stuck in recovery forever. If I try to press start, nothing happens. If I scroll up to factory, nothing happens either. If I look at the Bootloader logs, all it says is "failed to validate system image. Boot up failed".
The one good thing is that the phone recognizes being plugged into my computer (Windows 10), so maybe there's a small chance I can get my phone back. If you guys have a solution, please let me know, as I'm pretty distraught right now. Also hoping there's a chance I can get my photos back that are on the device, though that seems unlikely now.

Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.

ChazzMatt said:
Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.
Click to expand...
Click to collapse
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.

Xpwnage123 said:
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.
Click to expand...
Click to collapse
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Also with custom ROMs you can still run the ROM and UNroot your phone. (I know you can with CM.) No need to go back to stock, unless parent company of Pokemon is clueless and demands stock.
Well, seems they are clueless and doing what Android Pay does:
http://www.xda-developers.com/lates...blocks-rooted-devices-from-entering-the-game/
What Niantic has managed to do with the update is kill off the enthusiasm in users who had root but were not cheating. Root is used for many more things outside of cheating in a game, and to assume that all rooted users are cheaters is just silly.
_____
After some more reading around, it seems Niantic is actually using the SafetyNet checks to check for root. XDA Senior Member MaaarZ found the SafetyNetService being called in the game code. Niantic is really making users jump through the whole nine yards, as this is the same method employed by Android Pay. This means that if you do need to run Pokémon GO on a rooted device, you need to go through the whole Magisk and systemless root way. Or stop playing completely, because that is what Niantic wants you to do.
Click to expand...
Click to collapse

ChazzMatt said:
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Click to expand...
Click to collapse
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.

Xpwnage123 said:
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.

Xpwnage123 said:
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.

ChazzMatt said:
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.
Click to expand...
Click to collapse
TheSt33v said:
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.
Click to expand...
Click to collapse
Thank you guys. I was able to revive my phone from the dead using your advice. Unfortunately, I lost all of the photos from my trip to Europe, but overall I'm happy my phone is back and running. That will be a lesson to me to be less lazy about backing up my data.
Once again, thank you very much.

Someone over in Resurrection Remix thread got Pokemon Go to work with Root Cloak:
Nitefire77 said:
Pokemon go works on my phone with rootcloak. Wasn't too difficult to get it working
Click to expand...
Click to collapse
You can ask him for details. So, you can still run a custom ROM if you wish...

Stuck on marshmallow forever??

I wonder if anyone else is having my kind of issue? I spoke to Huawei support through the HiCare app last week. I enquired about emui 5.0 coming to the p9 in the UK. They told me it has been rolling out in waves for the past 5 weeks and it will make its way to me as soon as but could be as late as june. I mentioned that it is C432 software running on my phone and I asked them could they not push it manually to my phone. They told me no they can't do that, it has to be approved by all the networks first, even if my phone is unlocked and running C432 software. I also mentioned that it is on B166 and it's security patch was dated june 2016, they didn't seem to bothered by that. So I came on here and managed to flash B182 and that worked so I tried to move on to a package with emui 5.0 and all the ones I tried fail whilst installing and there is still no update available on the phone. Am I going to be on Marshmallow forever? Sorry for the rant.
Cheers

Just do it yourself manually then....
I used this guide and it worked fine... https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2
Went from B182 to B361 and the phone then updated itself to B378 straight away (which is the recommended route)
If you then want to root, you can flash TWRP & the special SuperSU from here... https://forum.xda-developers.com/p9/development/twrp-t3565703
Easy as 3.141592...

I might end up doing that. I didn't want to go down that route as I didn't have a lot of success with that last time. Thanks for the reply.

colthekid said:
Just do it yourself manually then....
I used this guide and it worked fine... https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2
Went from B182 to B361 and the phone then updated itself to B378 straight away (which is the recommended route)
If you then want to root, you can flash TWRP & the special SuperSU from here... https://forum.xda-developers.com/p9/development/twrp-t3565703
Easy as 3.141592...
Click to expand...
Click to collapse
Is it not fairly easy to brick the phone using these non OTA methods?

tmohammad said:
Is it not fairly easy to brick the phone using these non OTA methods?
Click to expand...
Click to collapse
In my opinion... No. Not if you follow the guides/rules.
No offence to anyone intended, but I think most problems are caused by people flashing the wrong rom/package without really searching & checking its the correct one. How many times do you see posts/threads on here asking questions that were answered a couple of posts before or in the previous thread?
I've been flashing roms and stock updates on various model phones for quite a few years and never had any issues like soft bricks. A few bootloops granted, but never a brick! I always follow the guides people on here write, to the letter, even though I'm sure I know enough to work it out myself.
And what's more important, I have my "disaster recovery" planned and ready...just in case things do go pear shaped!
Edit: This being a prime example!!! .... https://forum.xda-developers.com/p9/help/huawei-p9-bricked-t3587568

colthekid said:
In my opinion... No. Not if you follow the guides/rules.
No offence to anyone intended, but I think most problems are caused by people flashing the wrong rom/package without really searching & checking its the correct one. How many times do you see posts/threads on here asking questions that were answered a couple of posts before or in the previous thread?
I've been flashing roms and stock updates on various model phones for quite a few years and never had any issues like soft bricks. A few bootloops granted, but never a brick! I always follow the guides people on here write, to the letter, even though I'm sure I know enough to work it out myself.
And what's more important, I have my "disaster recovery" planned and ready...just in case things do go pear shaped!
Edit: This being a prime example!!! .... https://forum.xda-developers.com/p9/help/huawei-p9-bricked-t3587568
Click to expand...
Click to collapse
I wish i was on C432. I'd be flashing nougat myself. I'm on O2 UK with C40B190 version. From what I've read i have to jump through a lot of hoops just to get to C432. Then I can go to Nougat. Was told updates were coming in March but nothing happened.......

wards5150 said:
I wish i was on C432. I'd be flashing nougat myself. I'm on O2 UK with C40B190 version. From what I've read i have to jump through a lot of hoops just to get to C432. Then I can go to Nougat. Was told updates were coming in March but nothing happened.......
Click to expand...
Click to collapse
It's quite long winded I'll grant you, but not especially difficult...
(and it would get rid of any bloatware rubbish that O2 may have put on the phone!)
1. Flash C432B136 from here... https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
2. Flash oeminfo from here... https://forum.xda-developers.com/p9/development/c432-oeminfo-flash-twrp-t3384903
3. Flash C432B136 again
4. Flash C432B182 from here... http://www.carbontesla.com/2016/11/download-huawei-p9-b182-marshmallow-update-europe/
5. Update to Nougat B361 then B378 using the link to the guide I posted above.... (https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2)
6. Nougat TWRP & Root if required (https://forum.xda-developers.com/p9/development/twrp-t3565703)
More detailed and excellent guide here... https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Apart from the debranding bit (Mine is a sim free unbranded p9) these are the guides I followed.

i will be doing this tonight....as feed up of waiting

wards5150 said:
I wish i was on C432. I'd be flashing nougat myself. I'm on O2 UK with C40B190 version. From what I've read i have to jump through a lot of hoops just to get to C432. Then I can go to Nougat. Was told updates were coming in March but nothing happened.......
Click to expand...
Click to collapse
I have have a L09 running C432B182 on my phone which was sourced from O2.
Should I not then automatically go to Nougat via OTA?

tmohammad said:
I have have a L09 running C432B182 on my phone which was sourced from O2.
Should I not then automatically go to Nougat via OTA?
Click to expand...
Click to collapse
Yes in due course, but it seems to be taking a while for the OTA to "arrive" on individuals phones, that's why people are doing it manually.
If you don't mind waiting then don't bother, it'll happen eventually.

tmohammad said:
I have have a L09 running C432B182 on my phone which was sourced from O2.
Should I not then automatically go to Nougat via OTA?
Click to expand...
Click to collapse
How am i on C40190 then if you got yours from O2 too. It makes no sense. I'll be debranding when i get some free time.

your instructions worked perfect for me thank you went from 166 > 182> 361> 378 just as described mine would not update either

colthekid said:
It's quite long winded I'll grant you, but not especially difficult...
(and it would get rid of any bloatware rubbish that O2 may have put on the phone!)
1. Flash C432B136 from here... https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
2. Flash oeminfo from here... https://forum.xda-developers.com/p9/development/c432-oeminfo-flash-twrp-t3384903
3. Flash C432B136 again
4. Flash C432B182 from here... http://www.carbontesla.com/2016/11/download-huawei-p9-b182-marshmallow-update-europe/
5. Update to Nougat B361 then B378 using the link to the guide I posted above.... (https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2)
6. Nougat TWRP & Root if required (https://forum.xda-developers.com/p9/development/twrp-t3565703)
More detailed and excellent guide here... https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Apart from the debranding bit (Mine is a sim free unbranded p9) these are the guides I followed.
Click to expand...
Click to collapse
Cheers pal. I've been doing my homework and will be following your guide. Just need some free time to do it. How long does it take roughly? Sorry for another question but do i have to enable OEM unlocking in the developer settings.

on every reboot the phone would take 5 mins i left mine connected to pc at all times

wards5150 said:
Cheers pal. I've been doing my homework and will be following your guide. Just need some free time to do it. How long does it take roughly? Sorry for another question but do i have to enable OEM unlocking in the developer settings.
Click to expand...
Click to collapse
Can't remember precisely, but if you allowed 20-30 mins for each rom flash (including reunlocking & reflashing twrp when needed etc) you'd probably be on the right side of the actual timing overall.
Read up on the instructions for each step, download everything you need in advance & I have a separate sdcard on standby with the b136 rom on it to start again from step 1 if things go pear shaped (you can do this up to the nougat step, after then you have to downgrade back to MM first)
Yes, enable oem unlocking and make sure you're confident on using adb/fastboot, unlocking the bootloader and flashing twrp.
Come back & ask questions if you have issues, although I'm not an expert (maybe an enthusiastic amateur!), so probably best to ask in the thread relating to the bit you had problems with.

colthekid said:
Can't remember precisely, but if you allowed 20-30 mins for each rom flash (including reunlocking & reflashing twrp when needed etc) you'd probably be on the right side of the actual timing overall.
Read up on the instructions for each step, download everything you need in advance & I have a separate sdcard on standby with the b136 rom on it to start again from step 1 if things go pear shaped (you can do this up to the nougat step, after then you have to downgrade back to MM first)
Yes, enable oem unlocking and make sure you're confident on using adb/fastboot, unlocking the bootloader and flashing twrp.
Come back & ask questions if you have issues, although I'm not an expert (maybe an enthusiastic amateur!), so probably best to ask in the thread relating to the bit you had problems with.
Click to expand...
Click to collapse
Cheers. I'll give it a go. Thanks for the advice. Not played around with flashing since i had a G300. Trying to remember it all and get the brain back in gear.

colthekid said:
In my opinion... No. Not if you follow the guides/rules.
No offence to anyone intended, but I think most problems are caused by people flashing the wrong rom/package without really searching & checking its the correct one. How many times do you see posts/threads on here asking questions that were answered a couple of posts before or in the previous thread?
I've been flashing roms and stock updates on various model phones for quite a few years and never had any issues like soft bricks. A few bootloops granted, but never a brick! I always follow the guides people on here write, to the letter, even though I'm sure I know enough to work it out myself.
And what's more important, I have my "disaster recovery" planned and ready...just in case things do go pear shaped!
Edit: This being a prime example!!! .... https://forum.xda-developers.com/p9/help/huawei-p9-bricked-t3587568
Click to expand...
Click to collapse
Completely agree.. People do not take time enough to read carefully not only the how-to or guides but the whole thread to read other users doubts or bad experiences to avoid fall in same errors... Rush=>possible errors...
So please take your time torl read carefully and make a checklist step by step quite easy amd safe to change chat and then flash full b136 and enjoy the updates!
But carriers shouks/could treat their customer better and release more frequently the official updates with their bloatware to avoid force people to find workaround....
Enviado desde mi EVA-L09 mediante Tapatalk
---------- Post added at 09:36 PM ---------- Previous post was at 09:34 PM ----------
tmohammad said:
I have have a L09 running C432B182 on my phone which was sourced from O2.
Should I not then automatically go to Nougat via OTA?
Click to expand...
Click to collapse
Ask for update thought the HiCare app... Try to ask for update there...
Enviado desde mi EVA-L09 mediante Tapatalk

And another prime example of not reading/searching... https://forum.xda-developers.com/p9/help/p9-stuck-166-to-to-rescent-version-t3588597
At the time of writing, this thread was the next to the one above!
I mean, seriously??!! Nevermind all the guides around, all it would've taken is a look here! Lol!
Rant over!

Sorry if this has been asked... I have a P9 (EVA-L09) on B134. I'm lost. There are so many different guides when searching... Any help would be great! It has been a long time since I've messed with any of this - Samsung S5 era.

Thanks for all the help. Managed to do this correctly yesterday.

The great adventure of rooting the XZ1C

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.

newbie warning: don't re-lock bootloader, and beware flashing any custom ROM. &OTA...

newbie warning: don't re-lock bootloader, and beware flashing any custom ROM. &OTA...
only modify a phone you are willing to throw away.......
##
pre-note: TWRP 3.3.1-0 -> fastboot boot twrp.img (this is temporary)
before doing anything, backup some little partitions: EFS, fsg, Vendor. Maybe others. You will need these to get back to a working stock.
##
$$
DO AT YOUR OWN RISK - I TAKE NO RESPONSIBILITY.
note added 2-27-2020: it may be that some problems with returning to stock are due to not (in TWRP) advanced wiping data, system, dalvik ART cache before flashing. You can do temp "fastboot boot twrp-3.3.1-0-payton.img" w/o quotes, and do it there. -changed/edited. don't use TWRP to flash a stock zip!
$$
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
newbie warning: don't re-lock bootloader, and beware flashing ANY custom ROM.
On the X4, the bootloader changes drastically between 8 and 9 as it introduces a dual file system which is used by OTA updates to alternate the live system, and as a backup if failure. It is not a true Treble system, only partial. You must not depend on being able to flash back and forth between O and P. If you update to P, stay there. I expect this to be exacerbated by those phones which update to 10, if that in fact happens(probably One/fi only). There is also much confusion as to which file system/setup any custom ROM uses, and thus, how you would get back to stock, if that is even possible. Be very careful and assure yourself that you are fully willing to lose permanently your new phone before you do anything. Please read posts in these forums.
I've seen many posts of folks, mostly noobs, who have flashed ANY custom ROM Lineage and are unable to get back to a working stock. Sounds super simple but apparently it's not. Best to assume that if you try things, especially Lineage, that you will never be able to get back to a working stock. Read a bunch of posts here and you will realize that.
I've also seen a bunch of folks on this phone, and other phones who have run a bat file to flash their phone which contains the line
"fastboot oem lock" or similar.
Don't do it!!! - This will lock your phone and you will never be able to do anything with it again. It is totally unnecessary to lock your phone. Folks who should know better are leaving bat files lying around with this command. If you use one of those bat files to flash your phone, just check and remove that command line. Else you will have destroyed your phone. That's one of those things that "sounds good" until you do it.
EDIT: You can run stock on a bootloader unlocked phone - I do it all the time - plays PoGo just fine. I don't know about banking apps - I don't use them as I assume any 10-year-old can and will hack my phone.
EDIT: 6Feb2020: folks are reporting taking a security OTA onto a modified phone and rendering their phone(s) unusable. Only take OTA to a pure unmodified (no Majisk ever on it)(etc)(no mods ever on it)(stock recovery)(etc) stock ROM. Heed this warning. All of these "temporary" mods leave traces that screw up the update process.
EDIT: this was successfully fixed. see: https://forum.xda-developers.com/moto-x4/help/ota-update-endless-fail-loop-ppws29-69-t4045771 my guess is only works if you haven't changed bootloader or file system - NO custom ROM.
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
Please do a lot of reading here before you try to modify your phone, unless you are totally willing to render it useless. A word to the wise.

Ahah ))) I bought today X4 with relocked BL and I it seems it was relocked after flashing LOS or similar )) )
Now I trying to recover it ))
Сan we boot phone to QC9008 (EDL) mode without testpoiint?

St.Noigel said:
Ahah ))) I bought today X4 with relocked BL and I it seems it was relocked after flashing LOS or similar )) )
Now I trying to recover it ))
Сan we boot phone to QC9008 (EDL) mode without testpoiint?
Click to expand...
Click to collapse
afaik, you can't. Return the phone and get your money back. There will probably be a bunch of these worthless phones put up for sale. If you can't return it you could try the suggestions of sd_shadow in other threads here, but I don't believe they were successful on the X4.

KrisM22 said:
afaik, you can't. Return the phone and get your money back. There will probably be a bunch of these worthless phones put up for sale. If you can't return it you could try the suggestions of sd_shadow in other threads here, but I don't believe they were successful on the X4.
Click to expand...
Click to collapse
OK. But I unbrick it. Now I have fully loaded system, but without WiFi ot mobile network.. It`s problem - I can`t turn on OEM unlocking.. (
Goшng to try to find solution
UPD. Everything work well now. But it my device I have custom stock flashed. Not sure it`ll work with LOS onboard

its to late for me

llue45 said:
its to late for me
Click to expand...
Click to collapse
Yeah, I know. You're one reason I posted this.

modified OP

change: from "Lineage" to "any custom ROM"

hi im thinking about buy this phone for 100 bucks used how i can verify this relocked bootloader problem ? in Developer Options ? if i cant switch to Oem Unlocking its broken ? to make sure this dont happen to me the one who its selling it to me says that already its updated to PIE , i want stock and root it just that after unlock the bootloader but if cant be unlocked i better move on . so my question is what really im looking for , when i get my hands on the phone before drop my money to the thin air because is not a store . and maybe never see this guy again in my life , i Live In The Caribbean Dominican Republic
People here are not so trusty . so i will appreciate if i can have some tips to know if im going to do a good Buy. Thanks In Advance .

JavaShin said:
hi im thinking about buy this phone for 100 bucks used how i can verify this relocked bootloader problem ? in Developer Options ? if i cant switch to Oem Unlocking its broken ? to make sure this dont happen to me the one who its selling it to me says that already its updated to PIE , i want stock and root it just that after unlock the bootloader but if cant be unlocked i better move on . so my question is what really im looking for , when i get my hands on the phone before drop my money to the thin air because is not a store . and maybe never see this guy again in my life , i Live In The Caribbean Dominican Republic
People here are not so trusty . so i will appreciate if i can have some tips to know if im going to do a good Buy. Thanks In Advance .
Click to expand...
Click to collapse
Good to not be trusting!!!! With this (or any) phone, I recommend you get only from a place (like ebay) where you can easily return it and get your money back. ebay can force a reluctant seller to refund your money. Assure that the seller has a 99% + rating and says they will accept returns and pay for return shipment, usually for 30 days. I don't think you can easily tell if it has been unlocked and re-locked - only that it works perfectly, or doesn't. You can check the ID of the ROM in your phone against the latest for your area by checking lolinet.
When you get it, check all functions and assure IMEI is present. check wifi, BT, etc etc. Make calls. Check that the phone works with the towers in your area and with a local SIM. etc etc. read here and find the things that folks having problems where it won't do things and assure your phone will do it. Install Pokemon Go on it and play it briefly to assure your phone hasn't been modified. I have no idea if any of these phone will work with any banking or payment apps, and each app will have it's own specific checks that it performs against the phone. Test what you will use. Fully. ASSUME NOTHING!!!
As far as rooting it and/or unlocking it, I would strongly advise against it. For this particular phone X4 I would determine that it works perfectly and then NOT modify it. Unless, of course, you are willing to throw your phone away and buy a new one without a second thought(most of us don't have that kind of money!). Mine happened to have been unlocked when I got it from ebay but it was on a stock 8.1 and it was able to, and did OTA update to the latest Pie stock ROM. Thus I was easily able to assure if was okay. It being unlocked seems to have affected nothing. I have never tried to root it or do anything to it (recovery or otherwise) as I read far too many posts of folks here who had rendered their phones incapable of returning to a working stock, and only on a limited custom. Not what I wanted. I have not heard of anyone successfully getting one of these phones back to a FULLY WORKING stock state.
The days of getting a phone and easily modifying it and then returning it to stock may be gone. Get a phone you will enjoy, and use it! Unmodified!!! Welcome to pre-Treble part1a . Expect a few years of growing pains.
I like my phone and enjoy not having to worry about whether a custom ROM will work and constantly be chasing updates and fixes. I use a case - I believe it is this one
https://www.ebay.com/itm/For-Motoro...hash=item33d89fee5a:m:mU5XV7jSj1TfD_kr-L4VT9g
which, so far, has protected it from several minor falls. I would never use any phone w/o a case!!!

But i think if the phone gets unlocked the bootloader and flash twrp making a backup of the stock recovery before just booting the twrp custom recovery then flash magisk on twrp on top of Stock PIE , After Of Course Make A Full Backup Of all partitions reboot and then on Stock PIE have ROOT. and never flash custom roms and never lock the bootloader and stock can be reflashed without problems with a script on linux with fastboot on bootloader-fastboot mode this plan can work , NO ? i had a E4 sprint and never had problems doing that
I need root for A Lot Of Things like Xposed Drivedroid Youtube vanced Adway ETC.
Can Anyone who is reading this have done this just root pie on this phone with unlocked bootloader ? and able to restore stock flashing it back with the retail firmware just to remove root and clean the stock and recovery ? or try to put android one ? the phone which im going to buy its the XT1900-6 retail brazil i already have the retail stock official pie rom ready to flash and with the script on linux with no fastboot oem lock anywhere .

added to OP: EDIT: 2-6-2020 folks are reporting taking a security OTA onto a modified phone and rendering their phone(s) unusable. Only take OTA to a pure unmodified (no Majisk ever on it)(etc)(no mods ever on it)(stock recovery)(etc) stock ROM. Heed this warning. All of these "temporary" mods leave traces that screw up the update process.

OTA issues
KrisM22 said:
added to OP: EDIT: 2-6-2020 folks are reporting taking a security OTA onto a modified phone and rendering their phone(s) unusable. Only take OTA to a pure unmodified (no Majisk ever on it)(etc)(no mods ever on it)(stock recovery)(etc) stock ROM. Heed this warning. All of these "temporary" mods leave traces that screw up the update process.
Click to expand...
Click to collapse
I posted a new thread on these OTA issues with the X4 at https://forum.xda-developers.com/moto-x4/help/ota-update-endless-fail-loop-ppws29-69-t4045771. I was never presented with an "option" to install the latest OTA, it just automatically attempted to install (apparently a FORCED update) and is continuing to do so and failing ad infinitum. That phone works, just getting constant failure notifications. Question is, how to stop the attempted updates?
The second identical phone (updated per Magisk OTA tutorial instructions) is borked, with no phone connectivity. Can these be recovered by wiping/flashing stock rom PPWS29.60-39-6-2 and get them operating again as stock? I can forego the OTAs if there's a way to stop them from screwing up the device.
I never had other than stock recovery on either of these phones, I always boot TWRP via fastboot to do mods.

EDIT: XDA system is stalling and caused double post. Sorry. Mod please delete.
-deleted by me -

@redwoodie , please don't post to this thread. I read all your threads/posts but have no information.
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
As to whether "x" strategy will work, you are certainly free to explore that on your own, in your own thread.
No one here knows. I am certainly not going to experiment on my own phone and run the likelihood of having to buy a new one. Folks like yourself keep showing up and doing just that because they are SURE it will work. But it hasn't.
Read all the posts.
There are very few folks left here on this forum. Once they have destroyed their phone, and tried a bunch of things, they move on.
THERE IS NO SOLUTION.
This thread is only to warn newbies.
I personally know nothing about the phone other than what has been posted by others.
Read it.
If you discover a true solution that allows a phone to work perfectly ON STOCK, please post it and you will make lots of folks happy, assuming it is repeatable.
However, no known solution.
But, again, you are free to explore solutions - just not in this thread, please. Thanks.

added paragraph at top:
$$
DO AT YOUR OWN RISK - I TAKE NO RESPONSIBILITY.
note added 2-27-2020: it may be that some problems with returning to stock are due to not (in TWRP) advanced wiping data, system, dalvik-ART-cache before flashing. You can do temp "fastboot boot twrp-3.3.1-0-payton.img" w/o quotes, and do it there. -changed/edited. don't use TWRP to flash a stock zip!

This guy is full of crap
KrisM22 said:
only modify a phone you are willing to throw away.......
NO FIX IS KNOWN FOR ANY OF THESE PROBLEMS. PHONE IS DESTROYED.
Please do a lot of reading here before you try to modify your phone, unless you are totally willing to render it useless. A word to the wise.
Click to expand...
Click to collapse
I've literally put so many different custom ROMs on this phone. I've bricked it, unbricked, hard bricked it and soft bricked it. Stop misinforming people bro. The Moto G6 I would say to be careful with but still I wouldn't make a post like this guy. The Moto x4 just requires a little prep to make it a full treble, GSI accepting, custom Rom beast. Plus there are a few official ROMs out there even Android 10 for the Moto x4 specifically. Don't be scared. Just research a lot and follow instructions
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
JavaShin said:
But i think if the phone gets unlocked the bootloader and flash twrp making a backup of the stock recovery before just booting the twrp custom recovery then flash magisk on twrp on top of Stock PIE , After Of Course Make A Full Backup Of all partitions reboot and then on Stock PIE have ROOT. and never flash custom roms and never lock the bootloader and stock can be reflashed without problems with a script on linux with fastboot on bootloader-fastboot mode this plan can work , NO ? i had a E4 sprint and never had problems doing that
I need root for A Lot Of Things like Xposed Drivedroid Youtube vanced Adway ETC.
Can Anyone who is reading this have done this just root pie on this phone with unlocked bootloader ? and able to restore stock flashing it back with the retail firmware just to remove root and clean the stock and recovery ? or try to put android one ? the phone which im going to buy its the XT1900-6 retail brazil i already have the retail stock official pie rom ready to flash and with the script on linux with no fastboot oem lock anywhere .
Click to expand...
Click to collapse
The op is a cracker Jack

Ims status not registered
Guys i flashed custom rom without taking backups of efs and all,so i ended up with ims status not registered because of that my volte is broken mine is retin.I tried to flash stock firmware but the imei is broken.Any way to fix this?

bumpsi since apparently folks are not reading this. mod a phone, likely lose it. relock a phone and def lose it.

2020 Guide to Root the XZ1C ?

Hi there !
So for the first time in years of ownership, I am interested in Rooting.
Naturally I searched around here, but could only find 2017 and 2018 threads with many problems and various bugs.
For an April 2020 guy, rooting is stock latest ROM, and interested in keeping stock but go rooted (mostly to block some Android trash) - What is the easiest way, can I have a link that is updated, or a paid tool I can buy and not mess with anything ?
Thanks a lot !

baboon23 said:
What is the easiest way, can I have a link that is updated
Click to expand...
Click to collapse
Crack on - https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510

SXUsr said:
Crack on - https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
Click to expand...
Click to collapse
Too much mess for my blood !
How much would It be to hire your service via screenshare ?
PM me please
Keep in mind I only want a root so I can disable some stock google trash with F-Droid apps.... I don't really need a new ROM, or do I ?

I rooted mine on stock just a few weeks ago.
All I did was unlock the bootloader, flash TWRP, then flash the latest magisk. I then used Titanium Backup to remove the bloat. It was quick and painless.

Thanks !
Which thread did you use as guide/link glossary ?

I didn't use a guide, just did it based on experience rooting my Sony devices from before. But I can write up something brief. How much knowledge do you have rooting devices?

baboon23 said:
Too much mess for my blood !
How much would It be to hire your service via screenshare ?
Click to expand...
Click to collapse
I wouldn't want to do it that way, and if you do it yourself you'll gain a little experience which makes restoring or further modding easier.
baboon23 said:
Keep in mind I only want a root so I can disable some stock google trash with F-Droid apps.... I don't really need a new ROM, or do I ?
Click to expand...
Click to collapse
If you want to root you need to unlock the bootloader, if you're unlocking your BL then it's advised to backup your DRM keys and restore them after unlocking your BL which is a one time process. Everything you need is in the thread I've linked to above.

Thanks SX. I have seen a lot of your work around here doing searches, and I'm honored that you reply to my question
I will have a crack at it, I have done those things before but I remember not leaving the house for a few days, so it scarred me a bit
Haha
One last question if I may.... Do you believe that installing Lineage with no google on the xz1c is worth it? I guess it's a general question, but what I'm really asking is, should I even bother with rooting for privacy if my end goal isn't to flash Lineage ?

OK, after some more research, I have decided that what I really want to do is just install the 17v LineageOS version for the XZ1C.... It is my understanding it is possible without a root. ?
For sure the bootloader needs unlocking and TWRP to backup/flash correct ?
Super SU, does that make my procedure easier in any way ?
It is my understanding that if I flash a Lineage OS after unlocking via code and flashing TWRP, then the camera and all will still work.
Considering I don't mind binning that phone if I get sick of Lineage (I have like four of those in a box) - Can I skip the TA backup and restore ?
Apologies for the newb questioning, just trying to "get the hang" of it so I actually understand what i'm doing rather than just follow guides.
I'm a bit older than all you guys so forgive me

I'm running lineage 16.1 on root with unlocked bootloader without restoring TA. But I didn't care about preserving the keys. Yes camera works great and everything is super stable.
You don't have to root lineage so if you need help best to narrow down what exactly you want to do as there are many possibilities.

betacrypt said:
I'm running lineage 16.1 on root with unlocked bootloader without restoring TA. But I didn't care about preserving the keys. Yes camera works great and everything is super stable.
You don't have to root lineage so if you need help best to narrow down what exactly you want to do as there are many possibilities.
Click to expand...
Click to collapse
Absolutely, you're right !
I will be as specific as I can:
Sony abandoned the XZ1C, so I want to swap to Lineage OS with a full heart with no Gapps (i'll manage).
Here is what I understand tell me if I am correct:
1. Unlock bootloader via sony website
2. Flash latest TWRP
3. Use it to flash 17.1 Lineage OS from the genius dude (mod punk?)
4. Happy days
5. If modpunk updates it, will I be able to update with no reformatting ?

baboon23 said:
Absolutely, you're right !
I will be as specific as I can:
Sony abandoned the XZ1C, so I want to swap to Lineage OS with a full heart with no Gapps (i'll manage).
Here is what I understand tell me if I am correct:
1. Unlock bootloader via sony website
2. Flash latest TWRP
3. Use it to flash 17.1 Lineage OS from the genius dude (mod punk?)
4. Happy days
5. If modpunk updates it, will I be able to update with no reformatting ?
Click to expand...
Click to collapse
Yep that's about right. Unlock bootloader with Flash Tool by getting unlock code from Sony. Flash TWRP in fastboot mode. Boot to TWRP and flash lineage 17.1. If you don't need gapps you're good to go.
As for lineage updates probably best to check with the thread. Usually you can dirty flash, i. e. flash new version over the old and it should be ok. Lastly check to see if they're are any major bugs with 17.1. Since it's so new there could be issues. 16.1 is smooth fast and stable if you ever need to go back to it.

betacrypt said:
Yep that's about right. Unlock bootloader with Flash Tool by getting unlock code from Sony. Flash TWRP in fastboot mode. Boot to TWRP and flash lineage 17.1. If you don't need gapps you're good to go.
As for lineage updates probably best to check with the thread. Usually you can dirty flash, i. e. flash new version over the old and it should be ok. Lastly check to see if they're are any major bugs with 17.1. Since it's so new there could be issues. 16.1 is smooth fast and stable if you ever need to go back to it.
Click to expand...
Click to collapse
Superb, thank you so much ! What a wonderful community. I feel like im stealing. I will be sure to donate !
One question, may I use adb tools for the bootloader ?

No problem. That one I'm not sure about. I've only used flash tool myself but adb tools should work with the right commands.

Yay for me !
Bootloader unlocked, onto recovery and LOS

I did it !
Thanks yall
I get this horrible " please lock the bootloader" greeting when I turn on the device, for 5 seconds.
Is that normal for everyone ?

baboon23 said:
Considering I don't mind binning that phone if I get sick of Lineage (I have like four of those in a box) - Can I skip the TA backup and restore ?
Click to expand...
Click to collapse
You've got 4 XZ1Cs in a box?
baboon23 said:
I get this horrible " please lock the bootloader" greeting when I turn on the device, for 5 seconds.
Is that normal for everyone ?
Click to expand...
Click to collapse
It is yes, you'll have to live with that unfortunately. In regards to the TA, I would have taken the time to back them up, that'll matter should you wish to return to stock. It's better to have it and not need it than to need it and not have it. But you've achieved what you wanted to which is all that matters. :good:

Thank you sir !
You're probably right, I just couldn't be bothered... Sometimes 20 minutes more is like a life long more
Well, now that all is installed....
So when modpunk stopps working on the project (like sony stopped working on the xz1) - Will it be safe to just continue using the phone without updates at all ?
Or is the eventual doom of all ROM Flashers is to come back to stock (but then, it doesn't get updates anymore also...)
So does it matter in which platform I remain outdates ?
Re the XZ1's, I knew that this was going to be the last proper small phone so I made sure to stock. I plan to carry these into 2022 …….
Problem is, I think even in box without, the batteries will die out. So I'm not sure how smart I was when I got several.
All in all, for all phones I paid less than one iPhone so I'm pretty happy, but hopefully a lab can change the batteries on them.

baboon23 said:
Thank you sir !
You're probably right, I just couldn't be bothered... Sometimes 20 minutes more is like a life long more
Well, now that all is installed....
So when modpunk stopps working on the project (like sony stopped working on the xz1) - Will it be safe to just continue using the phone without updates at all ?
Or is the eventual doom of all ROM Flashers is to come back to stock (but then, it doesn't get updates anymore also...)
So does it matter in which platform I remain outdates ?
Re the XZ1's, I knew that this was going to be the last proper small phone so I made sure to stock. I plan to carry these into 2022 …….
Problem is, I think even in box without, the batteries will die out. So I'm not sure how smart I was when I got several.
All in all, for all phones I paid less than one iPhone so I'm pretty happy, but hopefully a lab can change the batteries on them.
Click to expand...
Click to collapse
I believe it is recommended to charge lithium-ion batteries fully every other month or so to keep it healthy.
If you are rooted I recommend checking out the ACC magisk module and controller app. This allows the phone to stop charging when the battery level has reached a certain level. In the long run keeping your device charged between I think 80% - 20% will increase your battery longevity by 200% (sorry I don't remember the exact study this was from).
And I agree the XZ1c is the last proper small phone. I've rebuilt mine from one sold for parts from eBay and now it feels like new.
About the security:
If you want to you can keep a look out for specific vulnerabilities in Android after the last security patch released for the custom rom.
https://source.android.com/security/bulletin
But in general by not connecting to sketchy WiFi hotspots, being un-rooted, having se-linux on enforcing, and running af-wall (requires root permissions) or another firewall you should be good for a while.
I think it really depends on what security issues get discovered in the future and what vulnerabilities your specific use case opens you up to.

Hi guys !
What about DRM key backup ?
I need help if you have a solution
https://forum.xda-developers.com/xp...de-to-install-lineageos-17-1-scratch-t4136195
Thanks you !