Related
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.
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting. I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging.
jwils1236 said:
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting and wouldn't have bought it if I would have known (or at least not updated to Pie). I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging/impossible. Any help would be appreciated and if a solution is brought to light, I am gladly offering $. This could easily be considered a device with best hardware and when rooted, access to best software -- I didn't see significant enough improvements in Note 9 and figured by now the support from XDA community would be abundant for the exynos processor. Turning out ridiculous waste of money if I can't root it (already purchased silver carbon fiber skin, 256 GB Samsung Evo Select SD card, attachable portable wireless charging pack, etc.). Please help!
Click to expand...
Click to collapse
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Its just easy step
Things u needed before proceed
* SD card
*Magisk latest version
*Odin
* Twrp zip file
1. Reflash ur device with proper firmware
2. After done go download mode and flash Twrp zip on odin. After done reboot ur device to Twrp again
3. After boot up to Twrp go to Wipe and do a factory restore . After this done u must install Magisk or u will get official binary only after reboot to system
4. After all the step are followed u are good to go. Cheers
stonedpsycho said:
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Click to expand...
Click to collapse
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
Also, for anyone reading this with the same issue, extracting the boot image from stock firmware (can be done through command prompt/terminal dump or by extracting from stock firmware -- AP Odin file) and patching with Magisk will not flash or work/give root access either unless this device is fully unlocked -- OEM unlock doesn't matter, if RMM still says "Prenormal" in download mode.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I am quite sure it is still rootable on bootloader 6, so updating would be fine.
The trick to get the OEM toggle is a bit hit and miss, the guide below is the method that has had a higher success rate for me, if followed exacty as written.
https://www.google.com/amp/s/www.xd...-samsung-galaxy-s8-samsung-galaxy-note-8/amp/
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I ended up using Chimera Tool to bypass RMM state. Worked instantly. This seems to be a common issue for many Samsung devices, at least on Pie. Not sure there is an alternative solution, currently. Only one I could find for my device.
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.
Hi all,
I am trying to relock the bootloader on 3T, with no success. I want to do it because of too many apps nagging me or not working with unlocked bootloader
here's what I did to unlock in the past and relock:
unlocking:
- enable dev options, enable oem unlocking & usb debugging
- flashed TWRP & fastboot oem unlock from command line (don't remember which I did first)
- got my phone wiped which was an an unexpected surprise!
- bootloader unlocked, the fist of those lovely warning screens telling me so
- tried to root without success, so no custom ROMs for me
- lived with it like this for a while, too many apps telling me they won't work, decided to relock
- got latest stock ROM, flashed it via TWRP, wiped, tried to fastboot oem lock ==> success reported by CLI, BUT device still unlocked
- flashed just the 3t recovery img, wiped, fastboot oem lock ==> success reported by CLI, BUT device still unlocked
- tried the qualcomm unbrick tool after installing the recommended drivers, can't have it see my device maybe because it's not bricked or maybe some other reason, I don't know. it doesn't show up in the app. Will uninstall and reactivate driver signature checks soon unless someone explains me how to make the bloody phone show up ...
So at this moment I have a many times-wiped phone with latest 9.0.4 stock ROM whose bootloader won't lock back. I am quite at a loss. I haven't tried any magisk or similat, SuperSU at the time told me I am not rooted.
I am tearing out the few hairs I have left. Any help for this poor family man so that he may not be allowed to walk in darkness? (quote from Uninvited). Thanks
Why don't you use Magisk hide to hide root/unlock status to those apps instead of loosing root/adaway and more?
pitrus- said:
Why don't you use Magisk hide to hide root/unlock status to those apps instead of loosing root/adaway and more?
Click to expand...
Click to collapse
I have never investigated Magisk, I think I installed it at the tima but there was some problem with it so I uninstalled it and didn't think much more about it. The problem is, my phone is not rooted (even though I tried it failed, I unlocked the bootloader to root it in the first place but was not successful), only OEM unblocked. So, so to say, I'm stuck in the worst of the possible worlds except for a bricked device. unlocked with no apparent way to relock it, and not rooted.
I feel like my phone is in some strange state where the normal procedures do not work. If I could at least figure out what's wrong with the rooting, I could go the full way AND then, in case use Magisk. but at the moment I feel like there is a need to put the phone in a known definite state whichever it is and work from there. I'd be happy to revert to stock and locked and then redo everything when needed in the future.
How could I troubleshoot further or get to such a "known state"? many thanks
The thing you did wrong was using the outdated SuperSU method of rooting which is not supported anymore. You should just flash the latest Magisk zip of their github page and then you will have root with the possibility of hiding it for bank apps and others.
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
pitrus- said:
The thing you did wrong was using the outdated SuperSU method of rooting which is not supported anymore. You should just flash the latest Magisk zip of their github page and then you will have root with the possibility of hiding it for bank apps and others.
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Click to expand...
Click to collapse
Thanks pitrus, I'll have a look at it tomorrow and will update with what happened
MassiB said:
Thanks pitrus, I'll have a look at it tomorrow and will update with what happened
Click to expand...
Click to collapse
Hi, update. I installed Magisk but, seeing that it had a way to put the phone in EDL mode, instead of going full root I decided to go the other way around and try to make my phone as stock as possible and reserve the experiments to an unit other than my primary. So I used the Qualcomm "unbrick" tool, and was able to flash the OxygenOS version that came with it - a rather old Android 6 whose networking (wifi, mobile...) wasn't working. But an adb sideload of the latest version after having put the phone in recovery mode allowed me to restore the networking and to update to the last supported version.
Magisk made the difference in getting me out of the spot. Thanks for bringing it to my attention!
Long story, but after travails with an Amazon-purchased Oneplus 9 Pro due to it being locked (T-Mobile!) and them refusing to unlock it....
I went to OnePlus and got myself a OnePlus 10 Pro Unlocked. Still have the T-Mobile sim, though.
My question....
I have been out of the rooted phone scene for some time. I had a Oneplus 2 rooted and a Samsung Note 4 and 5 rooted. But things are different now, I'm gathering. Plus this is a new phone and I don't want to toss away hundreds of dollars by bricking it.
I used TWRP back in the day. Flashed many a custom rom back then. But with this OnePlus, I already unlocked it which... is that the same as rooting it? And what are the benefits of rooting / flashing roms vs just going with what is currently on this US phone (Oxygen 13 but not 13.1 yet)? I kinda want to see TWRP on here, and back up my whole set up into files I can then copy to my computer(s) for safety's sake. At least I liked that feature when I had it w/ the OP 2 and others.
Trying to get back up to speed in the world of rooting as it stands now.
Thanks.
TWRP on this device is really, "make of it what you will." It doesn't fully support this phone officially, and the leaked versions don't support device decryption, so you'll be forced to not use a passcode on your phone.
You don't need TWRP anymore, you just need to be careful and know what you're doing. There's guides for every model here, although they're all basically the same. Try to avoid flashing anything from your PC to the phone, just flash inside Magisk and BOOT images.
From my knowledge the reason for this is there's hidden partitions from OPPO all over the filesystem and normal flashers don't take this into account, anyone just trying to flash a full zip has bricked.
Which leads me to, there's no full recovery for this device that's free. If you brick a file and end up boot looping both slots, you're gonna have to pay for a restore. Even with TWRP, from what I hear, full backups sometimes fail to restore properly on this device.
TL;DR Be careful, read guides, you'll be fine. Rooting (on this device, with a lack of full recovery, hence no custom ROMs or Kernels) is really just used for audio mods, photo mods like free google photos, extensive app mods, etc. If you're not actively looking into any of these, stock Android is pretty solid.
Prant said:
TWRP on this device is really, "make of it what you will." It doesn't fully support this phone officially, and the leaked versions don't support device decryption, so you'll be forced to not use a passcode on your phone.
You don't need TWRP anymore, you just need to be careful and know what you're doing. There's guides for every model here, although they're all basically the same. Try to avoid flashing anything from your PC to the phone, just flash inside Magisk and BOOT images.
From my knowledge the reason for this is there's hidden partitions from OPPO all over the filesystem and normal flashers don't take this into account, anyone just trying to flash a full zip has bricked.
Which leads me to, there's no full recovery for this device that's free. If you brick a file and end up boot looping both slots, you're gonna have to pay for a restore. Even with TWRP, from what I hear, full backups sometimes fail to restore properly on this device.
TL;DR Be careful, read guides, you'll be fine. Rooting (on this device, with a lack of full recovery, hence no custom ROMs or Kernels) is really just used for audio mods, photo mods like free google photos, extensive app mods, etc. If you're not actively looking into any of these, stock Android is pretty solid.
Click to expand...
Click to collapse
Thanks for this.
I got as far as unlocking the phone and installing Magisk. But haven't gone further until I understand what the next step is.
Can I root non-destructively? Or is the phone wiped?
If you're unlocked and have Magisk installed, rooting is as easy as booting a patched boot image, then using Magisk to install it to your boot image. You have the choice of finding a matching one in one of the guides or pulling your own from a full zip.
It must match the firmware revision, I know for a fact personally that region matters little in case of NE2215/3, as you're only doing a one time boot.
I recommend @g96818 's guide here, you can find almost every firmware's boot image posted there if you prefer patch it yourself using Magisk or just boot an already patched one.
I have a 10 Pro (NE2215) rooted as a daily driver using TMO US.
Unlocked means 2 things in the android phone scene. Either it's carrier unlocked and can take any sim from any phone company or it bootloader unlocked which is needed to root and load custom roms.
There aren't any custom roms for the 10pro because of the lack of a full recovery system. Basically the ability to force full flash a stock rom in case the custom ROM soft bricks the phone. So that leaves rooting as the reason to unlock your bootloader.
I suggest reading the guide for rooting this phone, it's relatively easy. TWRP is unnecessary as it doesn't offer much without custom ROMs. Also you should back up everything on the phone that you don't want to lose because during the rooting process a factory reset will occur (android safety feature).