Database Users

Why one should never unlock the Motorola Razr HD bootloader (xt925) !

The pro & cons of unlocking the bootloader:
Pro: Install customs ROMS with custom kernels (basically that's it)
Cons: - Loosing warranty from Motorola & your carrier
- No more firmware upgrades (your IMEI is dropped out of Motorola databank)
- Little verity of quality custom ROMs or development (close to none) exist for the Razr HD
- Future upgrade to JB & KLP will never happened (this phone is listed as a potential candidate for KLP update)
- Keeping your xt925 beyond your 1 year warranty will still guaranty, a steady upgrades of firmware
- Can root a phone with bootloader locked (without loosing warranty - root is reversible)
- Legally (Motorola binding Bootloader unlock contract), you can't sell a BL unlock Motorola Razr HD phone !
If someone can add some Pro's to an unlock bootloader please do it..

Are you sure about the firmware upgrades? I read somewhere that's not the case.

I wish I had known all this before I unlocked my phone.

Are you sure about the firmware upgrades? I read somewhere that's not the case.
Click to expand...
Click to collapse
I spoke to Motorola & my carrier services, also read the warning details before the unlock process begins.
I wish I had known all this before I unlocked my phone
Click to expand...
Click to collapse
Same here..(I learned all that after the fact)

I'd add this to Pro:
If you're stuck on Rogers 49003 ICS because you flashed the ROM trying to get root, your best option to get anything above 4.0.4 is to unlock bootloader?

Perhaps a CWM install will be possible for those with unlocked bootloaders when updates come.
It seems that in one form or another an unlocked bootloader means being able to push all the new files in doesn't it? Is there any limitation on this phone, for example flashing a new modem or kernel?

Cons one by one:
itzik_man said:
- Loosing warranty from Motorola & your carrier
Click to expand...
Click to collapse
True, but obvious.
itzik_man said:
- No more firmware upgrades (your IMEI is dropped out of Motorola databank)
Click to expand...
Click to collapse
Nope. Even if you were not to receive OTA, which by the way is not true as I've observed on my Photon Q, you can still freely flash the new firmwares yourself ^^
itzik_man said:
- Little verity of quality custom ROMs or development (close to none) exist for the Razr HD
Click to expand...
Click to collapse
Depends on ones point of view. Usually a CM port means you get newer Android sooner.
itzik_man said:
- Future upgrade to JB & KLP will never happened (this phone is listed as a potential candidate for KLP update)
Click to expand...
Click to collapse
Why it wouldn't? Unlocking BLs has no impact on upgrade schedule.
itzik_man said:
- Keeping your xt925 beyond your 1 year warranty will still guaranty, a steady upgrades of firmware
Click to expand...
Click to collapse
No. That's solely on Moto / Google decision. They don't have to update it at all. (See Droid 3, Milestone 3, Motorola XT720 etc.)
itzik_man said:
- Can root a phone with bootloader locked (without loosing warranty - root is reversible)
Click to expand...
Click to collapse
Yes, although you have to be careful, because there are scirpts checking if you're rooted.
itzik_man said:
- Legally (Motorola binding Bootloader unlock contract), you can't sell a BL unlock Motorola Razr HD phone !
Click to expand...
Click to collapse
You can sue Moto for breaking laws. They can't forbid you doing that (don't know honestly how is that in US / Canada, but I doubt that seeing how it works with computer games).
So please, while for normal user not willing to flash custom ROMs it's true that they should not unlock the bootloader, don't spill nonsenses around that. It's just that when you unlock your bootloader, you're on your own when playing with the firmware. But when you have stock firmware back on it, nothing prevents you from getting the OTA.

don't spill nonsenses around that. It's just that when you unlock your bootloader, you're on your own when playing with the firmware. But when you have stock firmware back on it, nothing prevents you from getting the OTA.
Click to expand...
Click to collapse
Possible 90% of your response represent just false theories..
OTA is goneforever once you unlock your bootloader ! If & when you be able manually to install JB, still your IMEI (not registered with Motorola) wont OTA.
You can sue nobody ! it's a contractual agreement you "sign" when you agree to unlock BL !
And if you can't OTA, No future auto upgrades.
So, before you use a statement "don't spill nonsense" make sure you are talking sense...

At least on my O2 Germany xt925 I got the update OTA from ICS to JB after unlocking. Had to return to the stock bootloader because the OTA relies on it after rebooting though.

itzik_man said:
Possible 90% of your response represent just false theories..
OTA is goneforever once you unlock your bootloader ! If & when you be able manually to install JB, still your IMEI (not registered with Motorola) wont OTA.
You can sue nobody ! it's a contractual agreement you "sign" when you agree to unlock BL !
And if you can't OTA, No future auto upgrades.
So, before you use a statement "don't spill nonsense" make sure you are talking sense...
Click to expand...
Click to collapse
Once again.
A) The reason why the page says "no updates" is beacuse OTA updates only work when you're on stock firmware, which is unlikely when you have the bootloader unlocked. That's all.
B) There are things that such "agreement" cannot contain. Being unable to sell the phone is one of them in most countries.

I disagree from the op.
Every change to device firmware compromises the warranty, not just bootloader, read the agreements ... If you exploit a bug to have root access, you will have to fool everyone who will have contact with your phone so they don't see what you have done. Even if you try to "reverse" the root, you(or the program you use) will always leave a trace.

We should be promoting "unlock the world"
This is not to imply everything should be free, however if I own something it should be mine in every regard, that includes breaking it.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 03:13 PM ---------- Previous post was at 03:12 PM ----------
@skrilax thanks for you work on the a500.
Sent from my Galaxy Nexus using Tapatalk 2

I have xt925, first thing I did was unlock boot loader. Then I updated ota to Telstra JB. OP is misleading people.

Once again.
A) The reason why the page says "no updates" is beacuse OTA updates only work when you're on stock firmware, which is unlikely when you have the bootloader unlocked. That's all.
B) There are things that such "agreement" cannot contain. Being unable to sell the phone is one of them in most countries.
Click to expand...
Click to collapse
To end my part in this discussion: The limitations, restrictions & disadvantages of unlocking the bootloader are much greater then any benefit or gain under the current availability of development !

Darbness said:
I have xt925, first thing I did was unlock boot loader. Then I updated ota to Telstra JB. OP is misleading people.
Click to expand...
Click to collapse
Have you tried out lte tethering? It doesn't work on Rogers.

To epinter -
I disagree from the op.
Every change to device firmware compromises the warranty, not just bootloader, read the agreements ... If you exploit a bug to have root access, you will have to fool everyone who will have contact with your phone so they don't see what you have done. Even if you try to "reverse" the root, you(or the program you use) will always leave a trace.http://www.linuxmobile
Click to expand...
Click to collapse
I did not notice your response at first, now to the point -
Without any disrespect to the work, time & effort invested, the main point is being ignored by the developers: All comments I got on this OP didn't touched the number one reason of my suggestion to not unlock the bootloader: There in not really enough of a variety of development options today to justification the bootloader unlocked of the xt925.

Skrilax_CZ said:
Cons one by one:
Yes, although you have to be careful, because there are scirpts checking if you're rooted.
Click to expand...
Click to collapse
Can someone elaborate on this point; I read in another thread that when you remove all rooted apps and data, clear out the files left in /system, that there is still info stored stated if the device has ever been rooted, and that this can be cleared using an app on a PC (don't remember which) however when I looked at the app it was specific to the XT926 and thus I wouldn't be able to use it.
After a thorough clean of every rooted app and everything left behind by rooted apps, is there a known way (or assumed to be working way) on XT925 to erase the record of the root.
Also, assuming I was to get my phone back to that state and remove proof of root, what specifically do I need to do in order to be careful as stated... or is epinter correct in saying that there is always a trace left behind, and if so, is this a blatant trace or something that hasn't been of much concern for Motorola in the past when servicing phones?
Tombs1234 said:
At least on my O2 Germany xt925 I got the update OTA from ICS to JB after unlocking. Had to return to the stock bootloader because the OTA relies on it after rebooting though.
Click to expand...
Click to collapse
How would I return to a stock bootloader if I were to unlock mine and an OTA didn't work? How did you do it?

itzik_man said:
The limitations, restrictions & disadvantages of unlocking the bootloader are much greater then any benefit or gain under the current availability of development !
Click to expand...
Click to collapse
It's your decision whether to unlock the bootloader or not. I'm just saying (for other users) that many of the cons you wrote were absolutely incorrect.
PantsDownJedi said:
Can someone elaborate on this point; I read in another thread that when you remove all rooted apps and data, clear out the files left in /system, that there is still info stored stated if the device has ever been rooted, and that this can be cleared using an app on a PC (don't remember which) however when I looked at the app it was specific to the XT926 and thus I wouldn't be able to use it.
After a thorough clean of every rooted app and everything left behind by rooted apps, is there a known way (or assumed to be working way) on XT925 to erase the record of the root.
Also, assuming I was to get my phone back to that state and remove proof of root, what specifically do I need to do in order to be careful as stated... or is epinter correct in saying that there is always a trace left behind, and if so, is this a blatant trace or something that hasn't been of much concern for Motorola in the past when servicing phones?
Click to expand...
Click to collapse
I believe there is something stored in the pds partition. Or at least it is that way on Droid RAZR XT912 and you had to fix it to remove the remaining traces. Flashing FXZ is also a way how to get a clean stock firmware, but pds partition is not affected that way.
PantsDownJedi said:
How would I return to a stock bootloader if I were to unlock mine and an OTA didn't work? How did you do it?
Click to expand...
Click to collapse
I think he meant "stock firmware" instead of "stock bootloader"

So if that were the case on this phone, I wonder if doing a dd backup of the pds partition before rooting at ICS, for restoring after downgrade, would be the way to go. Assuming it restores properly, it would be a good thing to add to the sticky thread about rooting. I did a dd of all my partitions except for /data last night, but I'm already rooted.
hmm... I'm wondering if there's something inaccessable in /system or even the sdcard since they get mounted with fuse. My only other Android phone was the Galaxy S II which was pretty straightforward and dead simple to root and unroot. I was surprised to see the fuse module being used to mount anything when I got this one.

The original topic is here: http://forum.xda-developers.com/showthread.php?t=1857558
I don't know if there was a proper fix developed (haven't checked) on the RAZR.

[4.4.4] for [SGP521]

Is this Android 4.4.4 to SGP521?
Link

Exciting!

Yes, it is 4.4.4, and it will bring us the new Z3 UI, and some Z3 features.

Bird40 said:
Is this Android 4.4.4 to SGP521?
Link
Click to expand...
Click to collapse
Sure you are not being a bit previous? My Z2 is SGP512, not SGP521! Hope you are right though
UPDATE: Doh! Just realized that both are valid

Very good news

Finally!
Sent from my SGP521 using Tapatalk

The rumour-mill has gone scarily quiet.. I don't understand why, having subscribed to a "premium" product, we don't get "premium" service. Anyone prepared to stir the pot and get the rumours going again?

pdes said:
The rumour-mill has gone scarily quiet.. I don't understand why, having subscribed to a "premium" product, we don't get "premium" service. Anyone prepared to stir the pot and get the rumours going again?
Click to expand...
Click to collapse
Ok, try this one. They're not going to push the 4.4.4 and will go straight to 5L next year

New version
New version
Link

Has anyone been able to update? Mine just failes
Sent fra min D6503 via Tapatalk

Installed and working properly, we only need to root :good:

Bird40 said:
Is this Android 4.4.4 to SGP521?
Link
Click to expand...
Click to collapse
yes, i already got it, any one has recovery?

I managed to install it with dual recovery but I am having issues on mounting the system. Does anyone know how to?

chesterr said:
I managed to install it with dual recovery but I am having issues on mounting the system. Does anyone know how to?
Click to expand...
Click to collapse
But it is compatible? Now try but could

So, what do you guys think about this update? Is it really worth it? Curious to know.

The biggest reason for me to change was to get Remote Play to link with my PS4. Also, the applications button is now shifted to the middle of the bottom edge. Other than that, I haven't noticed any huge changes that blew me away.
Remote Play is pretty cool though, tried it out for a little bit last night and it was good enough to play Call of Duty campaign mode.

chesterr said:
I managed to install it with dual recovery but I am having issues on mounting the system. Does anyone know how to?
Click to expand...
Click to collapse
Need to modify the kernel ramdisk to make it insecure.

Moscow Desire said:
Need to modify the kernel ramdisk to make it insecure.
Click to expand...
Click to collapse
Yea it did ask me about ramdisk btw, guess I'm just gonna wait till PRF Creator tool to be updated,

chesterr said:
Yea it did ask me about ramdisk btw, guess I'm just gonna wait till PRF Creator tool to be updated,
Click to expand...
Click to collapse
Well, technically, it's not such a big deal, to swap kernels/ramdisk with an unlocked bootloader. It's a simple edit. But, at this point, it would mean unlocking bootloader, and losing DRM keys (still not sure what functions besides some lost advanced camera functions, not that anybody uses the camera anyhow except for skype).
Under the old rooting, it used an exploit to modify ramdisk, (and install the necessary apps), without unlocking bootloader via an exploit.
As for me, I will wait a couple weeks and see if there's a new exploit. If not, well, I will do the above method.

Moscow Desire said:
Well, technically, it's not such a big deal, to swap kernels/ramdisk with an unlocked bootloader. It's a simple edit. But, at this point, it would mean unlocking bootloader, and losing DRM keys (still not sure what functions besides some lost advanced camera functions, not that anybody uses the camera anyhow except for skype).
Under the old rooting, it used an exploit to modify ramdisk, (and install the necessary apps), without unlocking bootloader via an exploit.
As for me, I will wait a couple weeks and see if there's a new exploit. If not, well, I will do the above method.
Click to expand...
Click to collapse
Basically DRM keys are used to see if you have unlocked the device (in the past). So mainly for Sony to check if your warranty is still valid.
There is a tool that will backup your DRM keys though, and can restore it too. You just need root for that (just downgrade, root, backup keys and upgrade again) Just Google Xperia DRM backup and you're bound to find out

One Click Root?

Hey Im getting the Moto X Pure Editon and I was wondering if there are any viable one click root methods, or a way to root without unlocking the bootloader. I have read that one certain (very questionable) method that XDA is against (and rightly so) can be used, but I have no plans on going that route. Im certainly not new to unlocking a bootloader and am not against it. Ive had the original Moto X Developer Edition, and currently have the Nexus 6, but the whole void the warranty deal I would like to avoid if at all possible. If I could get root and use titanium backup and ad free I could be fine with that. That being said is there a way to root without unlocking the bootloader. And is there something like on the old Droid Razr where you could install a recovery while the bootloader is still locked. Yes I know google is my friend and I have looked but haven't seen anything. So my assumption is I will probably have to unlock the bootloader. But I did want to ask before I jumped and unlocked it, because if anyone would know I know I could find out on here.

pacman377 said:
Hey Im getting the Moto X Pure Editon and I was wondering if there are any viable one click root methods, or a way to root without unlocking the bootloader. I have read that one certain (very questionable) method that XDA is against (and rightly so) can be used, but I have no plans on going that route. Im certainly not new to unlocking a bootloader and am not against it. Ive had the original Moto X Developer Edition, and currently have the Nexus 6, but the whole void the warranty deal I would like to avoid if at all possible. If I could get root and use titanium backup and ad free I could be fine with that. That being said is there a way to root without unlocking the bootloader. And is there something like on the old Droid Razr where you could install a recovery while the bootloader is still locked. Yes I know google is my friend and I have looked but haven't seen anything. So my assumption is I will probably have to unlock the bootloader. But I did want to ask before I jumped and unlocked it, because if anyone would know I know I could find out on here.
Click to expand...
Click to collapse
No, no one has developed a method to root without unlocking the bootlader and i doubt there will be one anytime soon(if ever since it's so easy and is an unlocked phone)

Ok thank you.

pizzlewizzle said:
No, no one has developed a method to root without unlocking the bootlader and i doubt there will be one anytime soon(if ever since it's so easy and is an unlocked phone)
Click to expand...
Click to collapse
With the hassles Motorola gives people trying to get warranty support after unlocking the bootloader, it would actually be quite beneficial.

Unlocking bootloader does not void warranty completely!!! Software issues caused by the user are indeed not under warrenty anymore. Hardware related issues are.. I had 2 times screen blemishes and both times my screen got replaced for free. Great service from motorola.

bartjeh1991 said:
Unlocking bootloader does not void warranty completely!!! Software issues caused by the user are indeed not under warrenty anymore. Hardware related issues are.. I had 2 times screen blemishes and both times my screen got replaced for free. Great service from motorola.
Click to expand...
Click to collapse
Ok I have done that with other phones but I had read mixed results concerning the Moto X Pure. So if it is hardware related Motorola will honor the warrenty, software your SOL. But software we can always reflash the stock system and all.

pacman377 said:
Ok I have done that with other phones but I had read mixed results concerning the Moto X Pure. So if it is hardware related Motorola will honor the warrenty, software your SOL. But software we can always reflash the stock system and all.
Click to expand...
Click to collapse
If you unlock boot loader ur self. Theres a oneclick root app calles kingroot they quote they can root amy phone its one of those china made apps and closed source, id only use ir if your that desperate. Also they install there own version of supersu.. but theres a way to remove it just.google it..

Kingroot doesn't work. At least it didn't on mine. Only way I've found is either systemless or toolkit if you're on lollipop

Jay794 said:
Kingroot doesn't work. At least it didn't on mine. Only way I've found is either systemless or toolkit if you're on lollipop
Click to expand...
Click to collapse
well i found this https://www.search4roots.com/how-to-easily-root-moto-x-style-marshmallow-6-0-1/

StreetkillnHD said:
well i found this https://www.search4roots.com/how-to-easily-root-moto-x-style-marshmallow-6-0-1/
Click to expand...
Click to collapse
I'd stick with the tested and tried methods. One click options have the potential for opening the doorway to unwanted content.....
Chainfire's supersu has been around for a long time.

Unlocking the bootloader is a must if you want to root on this phone... ATM anyway and I doubt it will change. I used to think one click root was the way to go too but once again, there are potentially many things that can go wrong so knowing the tried and true manual ways is always best. Knowing how to recover from botched attempts has allowed me to bring my phone back from soft bricks several times.
Sent from my awesome phone!

[discussion][root] with [locked bl], vulnerabilities Snapdragon on <March2016 Android

[discussion][root] with [locked bl], vulnerabilities Snapdragon on <March2016 Android
There's an interesting article that got me thinking:
http://buysoft.greatsoftline.com/vu...m-snapdragon-chip-allow-for-easy-root-access/
CVE-2016-0819 vulnerability
Click to expand...
Click to collapse
We discovered this particular vulnerability, which is described as a logic bug when an object within the kernel is freed. A node is deleted twice before it is freed. This causes an information leakage and a Use After Free issue in Android. (UAF issues are well-known for being at the heart of exploits, particularly in Internet Explorer.)
CVE-2016-0805 vulnerability
This particular vulnerability lies in the function get_krait_evtinfo. (Krait refers to the processor core used by several Snapdragon processors). The function returns an index for an array; however, the validation of the inputs of this function are not sufficient. As a result, when the array krait_functions is accessed by the functions krait_clearpmu and krait_evt_setup, an out-of-bounds access results. This can be useful as part of a multiple exploit attack.
Gaining root access
Using these two exploits, one can gain root access on a Snapdragon-powered Android device. This can be done via a malicious app on the device. To prevent further attacks that may target either the patched vulnerabilities or similar ones that have yet to be discovered, security experts are not disclosing the full details of this attack.
Trend Micro researchers will disclose the full details of exactly how to leverage the bugs at the upcoming Hack In The Box security conference in the Netherlands to be held in late May 2016.
Click to expand...
Click to collapse
Once updates got applied,
flashing back via XperiFirm, exploit that vulnerability and gain root
What do you think ?
langeveld024 said:
It was already found.
.11 fw is vulnerable at several points, however, rooting is not possible due to dm-verity and Sony ric which prevents modify system.
If u search this thread you'll find more about it.
Click to expand...
Click to collapse
bummer
Pandemic said:
We are genius in Z3 forum !!!!
http://forum.xda-developers.com/showthread.php?p=65856403
“Sent From MWE V9.5.0 On My Z3”
Click to expand...
Click to collapse
There's progress on the Z3 front

Poor Sony's fan waiting root for locked BL so long, many 6.0 phone have got root already,

Gaining root with locked BL is actually great security risk, not something one should be proud of.

Saw this?
http://forum.xda-developers.com/showthread.php?p=65861217
Post 1677 by Pandemic
It looks promising, the Z3 just got Root on LB
Thx. Wolfbreak the developer since the X10i
Sent from my E6653 @ XDA Portal

Duvel999 said:
Saw this?
http://forum.xda-developers.com/showthread.php?p=65861217
Post 1677 by Pandemic
It looks promising, the Z3 just got Root on LB
Thx. Wolfbreak the developer since the X10i
Sent from my E6653 @ XDA Portal
Click to expand...
Click to collapse
Is it possible to port this root method on M with LB for z3 ????? They have the same problem with DRM keys like us.... But they win.
http://forum.xda-developers.com/z3/...oid-6-0-mm-t3337357/post65856403#post65856403
thanx.

I don't think there will be a way to root z5 with LB unfortunatelly.

The method there needs a custom recovery installed which is possible on Z3 due to an exploit used on an early firmware. Since there's no such achievement yet on the Z5 you will already fail with the first task and any other following.
Since they've made their success public before the final firmware is out Sony has enough time to fix everything else.

some people say the z5 and z3 use the same hardware and could technically use the z3 rom to root the z5.
however, the heading of this post should change. i thought we finally have root on the z5 family only to find out that it's just a post talking about root on the z3.....

zacharias.maladroit said:
There's an interesting article that got me thinking:
http://buysoft.greatsoftline.com/vu...m-snapdragon-chip-allow-for-easy-root-access/
Click to expand...
Click to collapse
I didn't know those information were to be disclosed in May, instead of being kept secret. Good news from our point of view...
I think that, if the vulnerabilities could be exploited also on the Z5 line (every exploit needs to be verified practically), then we could gain temporary shell root/system priviledge to backup the TA partition. If i remember well, we cannot achieve permanent root on locked bootloader, as the /system protection SONYric is embedded in the stock kernel image.
We would need some mobile flashing tool like this: http://forum.xda-developers.com/showthread.php?t=2334554

I think i misunderstood. The problem is the Verified Boot ("dm-verity") check introduced in Z3+/Z4 and Z5 line.
We cannot get permanent root because this would involve modified kernel (to write on /system partition), which would not boot using a Locked bootloader because of Verified boot process that uses an OEM key.
The whole process is described here: https://source.android.com/security/verifiedboot/verified-boot.html
Google intention is (or was) to allow the boot process, after a red warning, if the verification of the kernel image didn't succeed on a locked bootloader... But Sony devices bootloop without showing any warning and so the user is not allowed to continue (source: https://androplus.org/Entry/843/ thanks to the developer).
So, on locked bootloaders, it's impossible to have permanent root apps, xposed ,.... unless someone finds a hole in the bootloader (someone found a hole in Motorola's bootloader) or the OEM key gets copied and is used to sign modified firmwares...just exciting dreams.
Anyone, correct me if i'm wrong.

ninestarkoko said:
I think i misunderstood. The problem is the Verified Boot ("dm-verity") check introduced in Z3+/Z4 and Z5 line.
We cannot get permanent root because this would involve modified kernel (to write on /system partition), which would not boot using a Locked bootloader because of Verified boot process that uses an OEM key.
The whole process is described here: https://source.android.com/security/verifiedboot/verified-boot.html
Google intention is (or was) to allow the boot process, after a red warning, if the verification of the kernel image didn't succeed on a locked bootloader... But Sony devices bootloop without showing any warning and so the user is not allowed to continue (source: https://androplus.org/Entry/843/ thanks to the developer).
So, on locked bootloaders, it's impossible to have permanent root apps, xposed ,.... unless someone finds a hole in the bootloader (someone found a hole in Motorola's bootloader) or the OEM key gets copied and is used to sign modified firmwares...just exciting dreams.
Anyone, correct me if i'm wrong.
Click to expand...
Click to collapse
Personally, not having permanent root on a locked bootloader is fine with me. I just need temp root to back up TA partition.
I am pretty sure the rest of the Z5 owners who are not yet unlock are waiting to backup TA partition before doing anything else.
there already is a way to restore credentials to use the bravia engine and the sony goodies. but ultimately, people would like to keep their TA keys (something which they paid for) instead of losing them once they unlock bootloader.

frostmore said:
Personally, not having permanent root on a locked bootloader is fine with me. I just need temp root to back up TA partition.
Click to expand...
Click to collapse
Me too

ninestarkoko said:
I think i misunderstood. The problem is the Verified Boot ("dm-verity") check introduced in Z3+/Z4 and Z5 line.
We cannot get permanent root because this would involve modified kernel (to write on /system partition), which would not boot using a Locked bootloader because of Verified boot process that uses an OEM key.
The whole process is described here: https://source.android.com/security/verifiedboot/verified-boot.html
Google intention is (or was) to allow the boot process, after a red warning, if the verification of the kernel image didn't succeed on a locked bootloader... But Sony devices bootloop without showing any warning and so the user is not allowed to continue (source: https://androplus.org/Entry/843/ thanks to the developer).
So, on locked bootloaders, it's impossible to have permanent root apps, xposed ,.... unless someone finds a hole in the bootloader (someone found a hole in Motorola's bootloader) or the OEM key gets copied and is used to sign modified firmwares...just exciting dreams.
Anyone, correct me if i'm wrong.
Click to expand...
Click to collapse
I remember few month ago... Chainfire was working with a new form of root, it doesn't modifies system partition. This solution doesn't help us???? We don't want lose our sony's features. :silly:

uripiruli said:
I remember few month ago... Chainfire was working with a new form of root, it doesn't modifies system partition. This solution doesn't help us???? We don't want lose our sony's features. :silly:
Click to expand...
Click to collapse
That's the systemless root, where root is achieve without changing the system file.
but this kind of root requires modified boot image, which cannot be done without unlocked bootloader....
root is becoming harder to achieve as the years pass. with samdung introducing their crap knox and sony with dm-verify etc etc.. android is fast becoming another apple where everything is being locked up and end users are forced to adhere to the way their phones are "supposed" to be used.

F U C K U P Sony. Why we couldn't own our phone features we paid for. Give our freedom to use our own phone

devilmaycry2020 said:
F U C K U P Sony. Why we couldn't own our phone features we paid for. Give our freedom to use our own phone
Click to expand...
Click to collapse
here's an article on the subject http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/
explaining your and my feelings (i really understand you).
If you want, you can comment there but please stay in topic here.

ninestarkoko said:
here's an article on the subject http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/
explaining your and my feelings (i really understand you).
If you want, you can comment there but please stay in topic here.
Click to expand...
Click to collapse
ok,thanks for told me about that. i'll be more attention about my words next times

Maybe developer Wolfbreak from the Z3 forum can help us?
Sent from my E6653 @ XDA Portal

Samsung Galaxy s7 and the edge exynos version just got root, wtf Sony --'.

I think the main thing about Samsung phones is they have a recovery partition where as sony do not.
Sent from my Xperia™ Z5 using Tapatalk

Searching For Root..

I've had this phone a little while now and I'm itching to root it. There's nothing wrong with it, I just really want to get into the code and do some modding. But there doesn't seem to be any root solution available right now.
So I thought I'd start this thread so we could discuss any rooting tips and ideas you all might have.
First I should probably mention all the potentially dodgy rooting solutions out there. Google "root xa1" and you get many results that offer methods to gain root access on our phone.
I confess I haven't tried any of them but that's because they all look suspicious. Some were written before the phone launched, some require you to download unknown software (I'll keep my PC virus-free, thanks), some even go so far as to feature a fake comment section with people saying it works.
I have no desire to stick malware on either my PC or my phone so I'm steering well clear of those.
The XZs launched at the same time as the XA1 and there seems to be a solution available for that. This is a thread by @zlRampageSlz with details: https://forum.xda-developers.com/xzs/how-to/tutorial-step-step-guide-to-gain-root-t3612624
It looks like the best solution is to unlock the bootloader (making sure to back up your TA partition first!), flash a modified kernel (otherwise the camera takes green pictures), flash a recovery image and then flash Magisk.
Where do we get this modified kernel? Where do we get the recovery image?
I have no idea, sadly. This is all way beyond my area of expertise. I'm a themer, not a developer.
But if anybody knows better than me, please post here.
This is a great phone, let's work together so we can get it modded!

Ticklefish said:
I've had this phone a little while now and I'm itching to root it. There's nothing wrong with it, I just really want to get into the code and do some modding. But there doesn't seem to be any root solution available right now.
So I thought I'd start this thread so we could discuss any rooting tips and ideas you all might have.
First I should probably mention all the potentially dodgy rooting solutions out there. Google "root xa1" and you get many results that offer methods to gain root access on our phone.
I confess I haven't tried any of them but that's because they all look suspicious. Some were written before the phone launched, some require you to download unknown software (I'll keep my PC virus-free, thanks), some even go so far as to feature a fake comment section with people saying it works.
I have no desire to stick malware on either my PC or my phone so I'm steering well clear of those.
The XZs launched at the same time as the XA1 and there seems to be a solution available for that. This is a thread by @zlRampageSlz with details: https://forum.xda-developers.com/xzs/how-to/tutorial-step-step-guide-to-gain-root-t3612624
It looks like the best solution is to unlock the bootloader (making sure to back up your TA partition first!), flash a modified kernel (otherwise the camera takes green pictures), flash a recovery image and then flash Magisk.
Where do we get this modified kernel? Where do we get the recovery image?
I have no idea, sadly. This is all way beyond my area of expertise. I'm a themer, not a developer.
But if anybody knows better than me, please post here.
This is a great phone, let's work together so we can get it modded!
Click to expand...
Click to collapse
First of all thank you so much for your awesome tool "Tickle My Android" which i really like it (Y).
i'm about to get XA1 Ultra so sure i'm so curious about root also but i'll try to make it clear,
simply, don't waste your time searching for a root tool because it's impossible to have root without modifying kernel, so, 100% all of these tools are just malware !
in the new devices there's something calls DM-Verity which is a check tool and that means any modification to /system will leads to bootloop,
so DM-Verity must be disabled ( through kernel of course ) & any mess with kernel means you have to unlock bootloader.
another thing, Sony ric which is prevent mounting system, so, any modification must be through recovery or it will leads to bootloop also, so we must also disable it.
fortunately on my xperia z2 there is no DM-Verity and there's a module to disable sony ric through recovery so root was possible without unlocking bootloader but starting from xperia z3+ DM-Verity appeared !
so now root is impossible without unlocking bootloader ( which means losing drm keys forever if you didn't back it up ).
i downloaded the firmware for xa1 ultra through xperiafirm and i unpacked the kernel and tried with these tools to see how its going on:
https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
&
https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893
the first one was hanging and i didn't get any information & the second one to be able to use it then you must put your ta.img ( your ta backup ) inside the folder,
i used my z2 ta.img as a test to see the process and the result was pretty good !
i successful disabled DM-Verity and there's no sony ric !!!!! but it's also still not safe and needs to be confirmed because maybe there's a bad surprise which is not clear yet, maybe something like sony ric but new !
so, if it's only the ****ty DM-Verity it's easy to disable it even away from this tool because we can't use it without ta.img, maybe by any script or unpacking kernel and modify it then repacking it this is not a problem at all & after that MAYBE we can flash supersu or magisk via ADB since there's no recovery yet ( completely not sure about this so it needs to be confirmed ) & in this case the choice is between root or drm features but at least root has been achieved.
so now, we need something like this to be able to backup ta without root and after that no problem of unlocking bootloader:
https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
or
https://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
or if it's not possible at this moment to backup ta without root then at least we need something like this to be able to to reactivate drm features such as camera denoise and x-reality...etc:
https://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
or
https://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383
or the worst choice...root without drm & waiting for a fix like those above !
anyway, root is not easy like before but it's still possible after all, i tried to clarify everything as much as i can and i hope there's a solution soon !
@munjeni we need your help bro, please if you have free time have a look, i uploaded the kernel for xa1 ultra so try to tell us how it's going on & what is new !
https://www.mediafire.com/?bc63fgjw99r785d
good luck for everyone .

As my Z5 compact was broken, I bought the XA1. I didn't remember, how awful an unrooted phone is - So I am also waiting and would be very interested to be informed.
BR
Sopur

Did anyone tried this?
https://www.oneclickroot.com/sony/sony-xperia-xa1/

chauhanjayc said:
Did anyone tried this?
https://www.oneclickroot.com/sony/sony-xperia-xa1/
Click to expand...
Click to collapse
I haven't, personally. Every mention of it I can find just looks like an advert. And I'm not paying for something that might not work and might do something horrible to my phone.
Sent from my Sony Xperia XA1 using XDA Labs

Ticklefish said:
I haven't, personally. Every mention of it I can find just looks like an advert. And I'm not paying for something that might not work and might do something horrible to my phone.
Click to expand...
Click to collapse
Its free

chauhanjayc said:
Its free
Click to expand...
Click to collapse
One Click Root does not work at the moment :crying:

kpfreak said:
One Click Root does not work at the moment :crying:
Click to expand...
Click to collapse
Uffffd
Let wait till next exploit.

chauhanjayc said:
Uffffd
Let wait till next exploit.
Click to expand...
Click to collapse
I'm sure it's only a matter of time.
Sent from my Sony Xperia XA1 using XDA Labs

bought this phone to replace my oppo. i can't wait for root abilities to be made

Bought this phone to replace my old Xiaomi. It's a good, powerful phone. Hope to see root appear for it soon. Personally for me, I'm one of those people who will only root a phone once it gets slow (the warranty expires). So as much as I'm reluctant to root my phone now, I'll hold out and see what wonderful developments appear on this thread.
Given the XA1 (I have the XA1 not the XA1 Ultra, I believe they are different) runs a Mediatek processor, I'm inclined to see something along the lines of a MT Flash Tool being used. Correct me if I'm wrong but I've only had successful flashes and roots with Qualcomm processors. The last device I had with a Mediatek processor (Lenovo A8-50 A5500H, MT8382) bricked on me horribly and I had to throw it away :crying:.
Meh. Hope we'll see awesomeness come soon from here. I'm still pretty new to XDA, looks like an awesome community

MINGXXIE said:
Bought this phone to replace my old Xiaomi. It's a good, powerful phone. Hope to see root appear for it soon. Personally for me, I'm one of those people who will only root a phone once it gets slow (the warranty expires). So as much as I'm reluctant to root my phone now, I'll hold out and see what wonderful developments appear on this thread.
Given the XA1 (I have the XA1 not the XA1 Ultra, I believe they are different) runs a Mediatek processor, I'm inclined to see something along the lines of a MT Flash Tool being used. Correct me if I'm wrong but I've only had successful flashes and roots with Qualcomm processors. The last device I had with a Mediatek processor (Lenovo A8-50 A5500H, MT8382) bricked on me horribly and I had to throw it away :crying:.
Meh. Hope we'll see awesomeness come soon from here. I'm still pretty new to XDA, looks like an awesome community
Click to expand...
Click to collapse
from what i've seen on sony's support page, they've made their own flash tool to flash stock roms to your phone with in case of events like bricking

diosdetiempo said:
from what i've seen on sony's support page, they've made their own flash tool to flash stock roms to your phone with in case of events like bricking
Click to expand...
Click to collapse
Is it? That's wonderful, shall go check it out

Seems like the ultra version has gotten it.
https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886

diosdetiempo said:
Seems like the ultra version has gotten it.
https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
Click to expand...
Click to collapse
Cool. I wonder if they can help with our device..
Sent from my Sony Xperia XA1 using XDA Labs

Hi. Wondered if I could ask advice. When trying to unlock bootloader using Sony website via a code. After entering the command with the code it says command not allowed, any ideas?

arienwalsall72 said:
Hi. Wondered if I could ask advice. When trying to unlock bootloader using Sony website via a code. After entering the command with the code it says command not allowed, any ideas?
Click to expand...
Click to collapse
I don't know, sorry. Did you definitely enter the right code?
Sent from my Sony Xperia XA1 using XDA Labs

Ticklefish said:
I don't know, sorry. Did you definitely enter the right code?
Click to expand...
Click to collapse
Yes. It gives the full command with the code on the Sony website. So I copied and pasted it from there. It does say on the phone in the service menu under bootloader unlock able = no. But says yes on the Sony website so not sure

arienwalsall72 said:
Yes. It gives the full command with the code on the Sony website. So I copied and pasted it from there. It does say on the phone in the service menu under bootloader unlock able = no. But says yes on the Sony website so not sure
Click to expand...
Click to collapse
if it says no on your phone then you're not able to

arienwalsall72 said:
Yes. It gives the full command with the code on the Sony website. So I copied and pasted it from there. It does say on the phone in the service menu under bootloader unlock able = no. But says yes on the Sony website so not sure
Click to expand...
Click to collapse
Go to Settings > About Phone.
Tap on Build Number until you get a toast notification that says you're a developer.
You should now be able to access Developer Options in Settings.
Go inside Developer Options then toggle OEM unlocking. Make sure it's on.
The code you get from the website should work now.