Related
Hello,
I had the impression of plenty of people unlocking their BL, like far more than 90%.
Now, as I thought about it, it came to my mind that I could be totally wrong about that.
Till now I thought, to unlock BL is like the normal thing to do, and maybe to relock if DRM was needed or DRM hack did not work.
Or, as in case with the latest DRM_Hack from Team HSxEXR, which is really cool! - if you forget to apply it after flashing, you maybe don't want to wipe data/factory reset after you already installed your apps.
So there are some cases where you just want to relock this thing.
But there are maybe some people who never unlocked it and went stock-based all the time? No custom kernels, no multiboot?
Since there is xposed, you can have a lot of things with any rom, if you can root and install a recovery. And there are the fantastic stock based ROMs which I prefered also a lot of the time, because of the better camera.
What is/ was your choice? Feel free to explain I am really eager to know how many of you never unlocked for example! Did you encounter any problems or could you use all the tweaks you wanted to install?
Unlocked 10 minutes after i arrived home with my Z2 XD
I haven't unlocked it and I don't want it because I'm totally satisfied with my stock based rom.
I don't even use xposed.
On previous phones I did both but I haven't crossed anything that would make me want to do it on my Z2
I haven't unlocked my bootloader. I just found the stock experience satisfying and trusted that Sony would still upgrade the software, which they seem to be doing. I use the #nochromo ad-blocking chrome browser and dolphin with an ad-blocker plug-in, so apart from YouTube ads I'm not bothered for root. Emulators run fast, battery life is good, camera is great (if you mess about with manual settings) and benchmarking to 49000 on antutu for what it's worth. Also I have a sony tablet & sony 4k android TV so I've left them all stock so they talk to each other fluidly. MM is only weeks away so I'm not even going to bother flashing the beta rom. And for the record I flashed both my HTC One X and HTC Desire multiple times, to account for the shortcomings in those devices. The shortcomings in the Z2 are so niggly and small that I don't see the point, in fact I have gone sim-only with my provider and refused an S7 Edge upgrade cos I like the Z2 so much!
:silly:
Kept a locked bootloader, only needed to have root.
Well,as for me,im too afraid to unlock the bootloader or even root.First,because im a heavy noob,i dont understand nothing ,even when you explain me,i will be like a girl which says "Ehmm,okay......".
The only thing i did is flashed my phone,thats the simpliest thing ever.My phone is still under warranty so i dont want to mess with stuff like that.
Unlocked it, the first day i got it.
Androplus kernel is must to get the full potential of the snapdragon.
I have LB, but sometimes I unlock for trying ROMs, I have a backup of my TA partition so I don't worry to unlock bootloader every time I want to try something
Enviado desde mi D6503 mediante Tapatalk
I did unlock my bl.
But I couldn't really notice a whole lot of difference, even with a custom kernel, so I relocked it by restoring my ta backup(make sure to take a ta backup no matter what). That was half a year ago though.
I might unlock it now that drm restoration is really easy, but I think that unlocking your bl does wipe your phone, and I am too bored to backup everything.
In all honesty, I don't think you are missing a whole lot by not having a custom kernel or a rom such as cm, as sony's software is already light enough.
However, I am guessing that there should be some gains via installing a custom kernel (overclock, or better battery life) so keep that in mind too.
Unlock and relocked several times already... No problems so far. Total freedom of choice....
Until the Xperia Z3, we still have the choice to keep bootloader locked since root exploit have been found.
But with Z4 then later Xperias you are forced to unlock your bootloader to root.
There won't be anymore root exploit for locked bootloader. We are lucky that Sony is allowing the unlocking of bootloader.
Envoyé de mon D6503 en utilisant Tapatalk
niaboc79 said:
There won't be anymore root exploit for locked bootloader. We are lucky that Sony is allowing the unlocking of bootloader.
Click to expand...
Click to collapse
Could you explain why?
Isn't it possible that new root exploits are developed in the future?
A root exploit is basically an unpatched security issue.
No system will ever be secure, there are possibly even root-exploits out there which are not shared with anybody
(Zero-day-exploit).
Anyways, I like the way Sony is opening their boot loader for public... It's like nexus.
Unlock after back my TA up, for safety
Knutselmaaster said:
Could you explain why?
Isn't it possible that new root exploits are developed in the future?
Click to expand...
Click to collapse
Nobody with requested skills care of Xperia devices anymore.
Envoyé de mon D6503 en utilisant Tapatalk
Unlocked the bootloader was the first thing I did, after testing the Z2 for a few hours only to see that everything works.
I didn't even bother to take a backup of those DRM keys. Never goig to use anything DRM related anyway.
I needed to flash a minimalistic ROM without bloatwares.
I've unlocked it a few times, but the worse photo quality always brought me back to stock. It's a shame we can't have the best of both worlds
Knutselmaaster said:
Could you explain why?
Isn't it possible that new root exploits are developed in the future?
Click to expand...
Click to collapse
XDA did a very nice article about this a while ago:
http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/
This line should be easy to understand: "In lieu of an unofficial bootloader unlock (those are fairly rare these days, short of leaked engineering bootloaders for a few Samsung devices), it seems highly unlikely that you’ll be getting root on Android 6.0 without some divine intervention – the combination of dm-verity (to stop your phone from booting with any modifications to the system partition), and the requirement for SELinux changes in the ramdisk (to let root work), look set to make things rather un-fun for root-aspiring users of these locked-down devices."
I'm so glad sony didn't enable dm-verity on the z2 mm beta or else root would be a HUGE problem for users with unlockable bootloader like me (z2 was my first sony device and i stupidly thought i could buy any z2 and request the unlock code from sony's dev site, so i bought it from vodafone at FULL price and got an unlockable bootloader as a bonus :crying: )
Like @niaboc79 said this things are EXTREMELY complex, technical and very hard to get around... and there's no one with the required skills on xperia sections as far as i know. I would gladly pay like 25/30eur to unlock the bootloader of my z2 if a sunshine like hack was available for it.
And to try and keep this still on topic i didn't unlock my bootloader just because i can't xD
I rooted my Z2 within a few days of owning it (coming from a Z1 which was a dud with horrible touch screen issues )
I proceeded to backup the TA partition and unlock the bootloader, and I have never relocked it, and I think it will stay that way for the foreseeable future.
To me, if the bootloader can be unlocked, it shall become unlocked
I'm currently on official CM12.1 with M5 Kernel, and that made me fall in love with the Z2 all over again, and funny enough this isn't the first time using a custom ROM like CM12.1.
I've used many ROMs on the Z2, from stock to custom and from KitKat to Marshmallow, and in the past there was always a catch in some way or another going to something like CM12.1 or anything based on it.
BUT, that isn't the case anymore.
Using official CM12.1 is just pure bliss. Literally everything is working just as well as on stock. It's like owning a Xperia Nexus, if such a thing existed
No random reboots. No lockups. No force closes. No errors. No bugs.
Awesome
So yes. Unlocking the bootloader was so worth it
Yes indeed, I also had a marvelous experience with 12.1 CM.
The only backdraw was that CM feels so "mainstream" and the ****ty "recovery".
This rom definetly ranges in the top 3 for z2 in my opinion.
There is one thing, that I miss on non-Sony ROMs if the camera is ok, and that is the small apps, yt/media-viewer in particular.
I don't like installing xposed if I don't have to, so the small apps are a nice way to listen to yt while screen off or using other apps in the foreground.
MOD EDIT by @gregbradley. I did not see the need for the expletive in the title, so i took it out for you.
So here's a little rant.
Read it if you'd like to, don't read if you don't like to.
Let's start with a little introduction. I've bought my Z3 about a year ago. I wanted to go with the z3+, but the Snapdragon 810 seemed to cause some issues. I still wanted the Sony batterylife after coming from a Galaxy S4 (which doesn't have the best battery life). I found online that Sony shares AOSP source code, so building a custom rom shouldn't be too hard.
Recently I have thought about unlocking my bootloader, but reading further into it, I found there to be NO upsides to unlocking your bootloader.
- There's a possibility of losing your DRM Keys when unlocking bootloader.
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Maybe I'm just nitpicking, but this seems very hypocritical from Sony..
C'mon Sony, your mobile department isn't doing too well, and this sure as hell doesn't make it better.
Now I know there are maybe only several thousand people actually wanting to run AOSP on their Sony, but I sure as hell am not buying another Sony phone until this policy changes.
Thanks.
Joost
Im still trying to figure out which part you unhappy about lol ?????
I have the Z3 rooted with Android 6.0.1 Slim1.6 Rom LB
And its the best ever with longest battery life ive experienced no issues fast and smooth
I dont want any other phone right now what more could you want?
MasterCMTS said:
Im still trying to figure out which part you unhappy about lol ?????
I have the Z3 rooted with Android 6.0.1 Slim1.6 Rom LB
And its the best ever with longest battery life ive experienced no issues fast and smooth
I dont want any other phone right now what more could you want?
Click to expand...
Click to collapse
My issue?
On one hand Sony releases AOSP code, while on the other hand they make it a real damn pain in the ass to even run an AOSP rom. There have been several developers out there to try and build an AOSP rom. None of them managed to make a fully working one, because Sony made it so damn hard. I find this hypocritical and unjust.
What I want is for Sony to make it actually possible to run an AOSP rom, and stop pretenting like it's possible.
Me Gusta said:
So here's a little rant.
Read it if you'd like to, don't read if you don't like to.
Let's start with a little introduction. I've bought my Z3 about a year ago. I wanted to go with the z3+, but the Snapdragon 810 seemed to cause some issues. I still wanted the Sony batterylife after coming from a Galaxy S4 (which doesn't have the best battery life). I found online that Sony shares AOSP source code, so building a custom rom shouldn't be too hard.
Recently I have thought about unlocking my bootloader, but reading further into it, I found there to be NO upsides to unlocking your bootloader.
- There's a possibility of losing your DRM Keys when unlocking bootloader.
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Maybe I'm just nitpicking, but this seems very hypocritical from Sony..
C'mon Sony, your mobile department isn't doing too well, and this sure as hell doesn't make it better.
Now I know there are maybe only several thousand people actually wanting to run AOSP on their Sony, but I sure as hell am not buying another Sony phone until this policy changes.
Thanks.
Joost
Click to expand...
Click to collapse
You can use TA Backup to restore your DRM keys as long as you back them up before unlocking the bootloader ('m just about to do it)
You can install a custom recovery via fastboot (I used TWRP to replace cyanogen recovery).
Not really sure your points to be honest.
savo83 said:
You can use TA Backup to restore your DRM keys as long as you back them up before unlocking the bootloader ('m just about to do it)
You can install a custom recovery via fastboot (I used TWRP to replace cyanogen recovery).
Not really sure your points to be honest.
Click to expand...
Click to collapse
Sure, you can restore DRM.. but is it really convenient? My point is that Sony basically promotes AOSP roms by releasing source code, but on the other hand they make it impossible to enjoy a fully working AOSP rom because of DRM, camera's never working, etc..
Oh, and if you could explain to me how you flashed TWRP, and which file exactly, that'd be great . I've literally already spent 6 hours today trying to figure **** out after unlocking my bootloader..
Thanks in advance!
I totally agree with you. Building an AOSP ROM for Z3 seems to be difficult (Tried cm too but extracting proprietary blobs did not work). The way how recovery works here is pretty stupid, seeing that we dont have a recovery on N for example, so I need to be on it without root (i dont blame developers here, but again, Sony's implementation). Also I haven't been able to work around the radio or camera thing in AOSP, even though I have only been able to build the ROM like once some weeks ago
---------- Post added at 06:00 AM ---------- Previous post was at 05:55 AM ----------
Me Gusta said:
Sure, you can restore DRM.. but is it really convenient? My point is that Sony basically promotes AOSP roms by releasing source code, but on the other hand they make it impossible to enjoy a fully working AOSP rom because of DRM, camera's never working, etc..
Oh, and if you could explain to me how you flashed TWRP, and which file exactly, that'd be great . I've literally already spent 6 hours today trying to figure **** out after unlocking my bootloader..
Thanks in advance!
Click to expand...
Click to collapse
Also the recovery thing. Just download the .img from Nailyk's thread and put it in ADB folder. Then go to fastboot and type fastboot flash FOTAKernel . Then boot to recovery by pressing power and volume down button, releasing power when phone vibrates and volume when sony logo appears.
Me Gusta said:
- There's a possibility of losing your DRM Keys when unlocking bootloader.
Click to expand...
Click to collapse
That is true and disappointing. However, there is a way to backup the keys and restore whenever the need arises.
Me Gusta said:
- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.
Click to expand...
Click to collapse
fastboot oem lock or restoring the DRM keys should relock the bootloader.
Me Gusta said:
- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!
Click to expand...
Click to collapse
Sure it works, you just need to run 23.4.A.1.264 firmware or newer. I use fastboot flash recovery something.img all the time.
Me Gusta said:
- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??
Click to expand...
Click to collapse
I think the Concept software is for those who don't need Sony enhancements (X-Reality, ClearAudio+, etc.) and want something that is close to stock.
So:
-You can backup and restore DRM functions even with an unlocked BL.
-You can relock BL again (haven't tried it myself but I think it's possible, if you check out DRM restoration guides I think they also show how to relock the BL)
-The new Sony BL allows fastbooting recoveries, the older ones support FOTA recoveries (I've used both with no problems)
-The MM concept project is still live, you can install it and continue using it, it gets updated regularly and is very close to AOSP.
-True Sony is kind of shady with their sources but you can build AOSP, there are AOSP builds for the Z3 here: http://fxpblog.co/ they get released whenever Sony releases new sources but you can also make builds yourself. The only true issue with sources comes out on certain AOSP functions and that we don't have (yet) fully working CM13 builds. As for the concept firmware it's exactly what you said, Sony is giving it out to people who are interested in having a close AOSP experience with support from the vendor while giving feedback to further improve it. Sony is making moves and is becoming more developer friendly by the month, other than new and constantly updated sources, proof of this is the Xperia Z3 is the only non-Nexus device that gets to run the Android N preview officially given from the vendor.
The Z3 is a great device, I personally haven't regreted the purchase, the only thing that bugs me is that neither I nor anyone else has managed to build a fully functional CM13 build (kudos to infected btw).
---------- Post added at 09:02 AM ---------- Previous post was at 08:58 AM ----------
Evokkimus said:
I totally agree with you. Building an AOSP ROM for Z3 seems to be difficult (Tried cm too but extracting proprietary blobs did not work). The way how recovery works here is pretty stupid, seeing that we dont have a recovery on N for example, so I need to be on it without root (i dont blame developers here, but again, Sony's implementation). Also I haven't been able to work around the radio or camera thing in AOSP, even though I have only been able to build the ROM like once some weeks ago
---------- Post added at 06:00 AM ---------- Previous post was at 05:55 AM ----------
Also the recovery thing. Just download the .img from Nailyk's thread and put it in ADB folder. Then go to fastboot and type fastboot flash FOTAKernel . Then boot to recovery by pressing power and volume down button, releasing power when phone vibrates and volume when sony logo appears.
Click to expand...
Click to collapse
As I said fxp has some builds, I haven't tested them but I think they work (http://fxpblog.co/)
I was eager to try out FXP's aosp ROM, due to 3.10 kernel and such, but I got an error about updater-script in META-INF, didn't read further. I have my suspicions that it was a bad download, but their current site is so slow to download from (about 2 hours to download, and only a +20kb/s faster if you register), and i'm not going to pay for that site. If it helps any, i just wiped data, system and caches and tried flashing the ROM.
---------- Post added at 12:14 PM ---------- Previous post was at 11:56 AM ----------
CedArctic said:
So:
-You can backup and restore DRM functions even with an unlocked BL.
-You can relock BL again (haven't tried it myself but I think it's possible, if you check out DRM restoration guides I think they also show how to relock the BL)
-The new Sony BL allows fastbooting recoveries, the older ones support FOTA recoveries (I've used both with no problems)
-The MM concept project is still live, you can install it and continue using it, it gets updated regularly and is very close to AOSP.
-True Sony is kind of shady with their sources but you can build AOSP, there are AOSP builds for the Z3 here: http://fxpblog.co/ they get released whenever Sony releases new sources but you can also make builds yourself. The only true issue with sources comes out on certain AOSP functions and that we don't have (yet) fully working CM13 builds. As for the concept firmware it's exactly what you said, Sony is giving it out to people who are interested in having a close AOSP experience with support from the vendor while giving feedback to further improve it. Sony is making moves and is becoming more developer friendly by the month, other than new and constantly updated sources, proof of this is the Xperia Z3 is the only non-Nexus device that gets to run the Android N preview officially given from the vendor.
The Z3 is a great device, I personally haven't regreted the purchase, the only thing that bugs me is that neither I nor anyone else has managed to build a fully functional CM13 build (kudos to infected btw).
---------- Post added at 09:02 AM ---------- Previous post was at 08:58 AM ----------
As I said fxp has some builds, I haven't tested them but I think they work (http://fxpblog.co/)
Click to expand...
Click to collapse
I also tried building CM but stuck on proprietary blobs part. Couldn't pull them from the device for some reason, even though i was on CM rom at the time. (I did it because breakfast ended up in some vendor errors and Z3 didnt show up on the list either)
Evokkimus said:
I also tried building CM but stuck on proprietary blobs part. Couldn't pull them from the device for some reason, even though i was on CM rom at the time. (I did it because breakfast ended up in some vendor errors and Z3 didnt show up on the list either)
Click to expand...
Click to collapse
Weird, I build CM12.1/CM13.0/twrp 3 with theMuppet repo without a glitch. Can you paste your compilation error in a pastebin or something like this? Maybe I can help you a little (I'm a compilation newbie)
nailyk said:
Weird, I build CM12.1/CM13.0/twrp 3 with theMuppet repo without a glitch. Can you paste your compilation error in a pastebin or something like this? Maybe I can help you a little (I'm a compilation newbie)
Click to expand...
Click to collapse
Basically the error I get is with extract-files.sh. When I run "./extract-files.sh" while phone is plugged in, I get permission denied. The other option for me is to run it with sudo, but then I get "line XX adb: command not found" (many lines of this error). Someone suggested chmod or opening a terminal window inside the folder where extract-files.sh is located. There shouldn't be any errors with my AndroidSDK path, even though some suggest the error is with this.
Also the reason I'm trying to pull these blobs, is because the CM tutorial told me so
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://wiki.cyanogenmod.org/w/Build_for_z3
------------------------------------------------------------
Also the reason I'm building CM is because I still don't know how to get radio working, even though a person has told how to get it working, I don't know how to exactly do it. But firstly I would like this CM thing to work. Thanks for your help.
Evokkimus said:
Also the reason I'm building CM is because I still don't know how to get radio working, even though a person has told how to get it working, I don't know how to exactly do it. But firstly I would like this CM thing to work. Thanks for your help.
Click to expand...
Click to collapse
No worries.
So it may be a little more complicated.... If you just need a functional self build CM, try to include themuppet repo. If your device variant is not currently officially supported it can be more complicated.
I suggest you to open (or find) a dedicated thread and quote me, or join #[email protected]
Otherwise I'm following this thread because I found some point really interesting. I'm currently in trouble with Sony, that's why I subscribe.
Sorry for off-topic answers.
sorry did not see the date
arminbih said:
sorry did not see the date
Click to expand...
Click to collapse
Customer service troubles. They didn't respect law about unlocked bootloader into my country and refused to fix my device.
I know this thread is basically dead but I figured I'd poke it with a stick a few times and give my two cents.
First of all, the reason I chose Sony. I peviously owned Galaxy S4 and at some point (Android 4.2.2?) they implemented a security software called KNOX. It lets you create encrypted partitions for business stuff. Soon after, users started reporting that any unofficial changes result in a "0x01" flag showing in the download mode. Turns out, the device has a physical e-fuse which is burned and can not be reverted (except with a motherboard change). It was mainly for the customer services to be able to tell if the phone had been tampered with. But here's the catch - it was also triggered when installing official Samsung firmware using ODIN (basically FlashTool or Emma for Samsung). And downgrading firmware to pre-KNOX resulted in a special lock - the inability to upgrade again.
XDA members, such as Chainfire and others, have not managed to crack the software after several years, despite the bounty of thousands of dollars. I didn't think much of it, and rooted. Months after that my phone stopped recognizing the SIM card. And since I had "0x01" I had no warranty. So it went to customer service many times, I paid for the SIM reader change, and still nothing. Even custom ROMs didn't help.
So, I had a phone with no SIM support, and no faith in Samsung. I found out that Sony "encourages Android development" - bootloader unlocking and so on. Soon after I bought a Z3, and being a power user, I wanted to root. And then I found out about the DRM. The more I researched, the more livid I got. Finally I managed to dig up a method of rooting without bootloader unlock. After every small update Sony issued, I had to go through hours of researching and developing a new cusom update for my device. After some time I just decided to go with a (back then unreliable) DRM function restoring flashable zip.When I heard there will be no Nougat for Z3, I was quite mad. I looked into some AOSP's. NONE of them were working correctly. So I settled with a Z3 on unlocked BL with some DRMs working. The device has hiccups but is usable. I am disappointed in Sony and I am disappointed in Samsung. Never buying their phones again.
But now that @nailyk is developing LineageOS for Shinano devices, we have new hope! :victory:
The Android Robot said:
I know this thread is basically dead but I figured I'd poke it with a stick a few times and give my two cents.
First of all, the reason I chose Sony. I peviously owned Galaxy S4 and at some point (Android 4.2.2?) they implemented a security software called KNOX. It lets you create encrypted partitions for business stuff. Soon after, users started reporting that any unofficial changes result in a "0x01" flag showing in the download mode. Turns out, the device has a physical e-fuse which is burned and can not be reverted (except with a motherboard change). It was mainly for the customer services to be able to tell if the phone had been tampered with. But here's the catch - it was also triggered when installing official Samsung firmware using ODIN (basically FlashTool or Emma for Samsung). And downgrading firmware to pre-KNOX resulted in a special lock - the inability to upgrade again.
XDA members, such as Chainfire and others, have not managed to crack the software after several years, despite the bounty of thousands of dollars. I didn't think much of it, and rooted. Months after that my phone stopped recognizing the SIM card. And since I had "0x01" I had no warranty. So it went to customer service many times, I paid for the SIM reader change, and still nothing. Even custom ROMs didn't help.
So, I had a phone with no SIM support, and no faith in Samsung. I found out that Sony "encourages Android development" - bootloader unlocking and so on. Soon after I bought a Z3, and being a power user, I wanted to root. And then I found out about the DRM. The more I researched, the more livid I got. Finally I managed to dig up a method of rooting without bootloader unlock. After every small update Sony issued, I had to go through hours of researching and developing a new cusom update for my device. After some time I just decided to go with a (back then unreliable) DRM function restoring flashable zip.When I heard there will be no Nougat for Z3, I was quite mad. I looked into some AOSP's. NONE of them were working correctly. So I settled with a Z3 on unlocked BL with some DRMs working. The device has hiccups but is usable. I am disappointed in Sony and I am disappointed in Samsung. Never buying their phones again.
But now that @nailyk is developing LineageOS for Shinano devices, we have new hope! :victory:
Click to expand...
Click to collapse
Lots of OEM are doing this stuffs to protect their intellectuals rights with DRMs. AFAIK oneplus allow bootloaders unlock.
Just for fun, the TA partition of sony contain so much things... It is crazy! BTW I think we have fuse too
idk where you live but in Europe there is a law which basically said: hardware and software are separated and OEM need to fix hardware, except if they can prove this is user fault.
1999/44/CE in date of 1999-05-31.
Today I updated my G4 to Nougat (downloaded via XDA) and discovered that the command "fastboot oem lock" works fine, so guys if you want to relock your device now you've an official option for this
TAKE NOTE: the command wipes the phone so MAKE A BACKUP before doing this!!!
You didn't discover anything; don't claim work you didn't do. You "discovered" it using my thread and/or YouTube video.
Its not a massive discovery and he could very well have found this without seeing your thread/video as could have anyone.
No need to be so hostile!
This is probably due to this release being v29 and not v30.
It is likely that the bootloader distributed with v29 is a test build and that this will not be as easy in the final V30 release.
LG probably overlooked it because they didn't expect it to be available to everyone.
The bootloader has also been relockable for some time through alternative means,
Re-Flashing the MISC partition (Personally tested) from a backup or extracted from a KDZ (Reported by others) will also re-lock your device.
OllieD said:
Its not a massive discovery and he could very well have found this without seeing your thread/video as could have anyone.
No need to be so hostile!
This is probably due to this release being v29 and not v30.
It is likely that the bootloader distributed with v29 is a test build and that this will not be as easy in the final V30 release.
LG probably overlooked it because they didn't expect it to be available to everyone.
The bootloader has also been relockable for some time through alternative means,
Re-Flashing the MISC partition (Personally tested) from a backup or extracted from a KDZ (Reported by others) will also re-lock your device.
Click to expand...
Click to collapse
I know it's not a massive discovery but he did take it from my video at least, before starting this thread he asked for details on YT and now he deleted the comments (need proof? I still have mails of comments). Maybe I should've not been so hostile but this kind of things bother me.
Appears to be a duplicate of [V29a only] I managed to relock the bootloader without any backups.
Better to have all the discussion in one place.
Thread closed.
Are You Like Me?
Have you remained Vigilant.. and kept your 7x a Virgin?
Untouched by the rough hands of another country's software.. resisting the unwanted pressures of your peers to unlock your chastity belt.. (A.K.A.) your bootloader.. to give in to what's been described as plethora of pleasure known as:
TWRP.. Root.. ROM's ( As Unstable As They Currently Are On The 7x )
Well..
I'm happy to say Gratification is just around the corner..
U.S.A. Variants ( BND-24) Versions of the 7x will recieve the "OFFICIAL AND 100% STABLE" release of EMUI / OREO 8.0 within the next 72 hours of this writing via an O.T.A. update from Honor.
I'm So Glad I Stayed Locked & Stock
Congratulations Honor!
You came through!!! :good:
RaiderWill said:
Are You Like Me?
Have you remained Vigilant.. and kept your 7x a Virgin?
Untouched by the rough hands of another country's software.. resisting the unwanted pressures of your peers to unlock your chastity belt.. (A.K.A.) your bootloader.. to give in to what's been described as plethora of pleasure known as:
TWRP.. Root.. ROM's ( As Unstable As They Currently Are On The 7x )
Well..
I'm happy to say Gratification is just around the corner..
U.S.A. Variants ( BND-24) Versions of the 7x will recieve the "OFFICIAL AND 100% STABLE" release of EMUI / OREO 8.0 within the next 72 hours of this writing via an O.T.A. update from Honor.
I'm So Glad I Stayed Locked & Stock
Congratulations Honor!
You came through!!! :good:
Click to expand...
Click to collapse
Unlocking the bootloader has nothing to do with taking ota, flashing a custom recovery does. People that rooted would have problems with taking the ota.
You State The Obvious..
EnIXmA said:
Unlocking the bootloader has nothing to do with taking ota, flashing a custom recovery does. People that rooted would have problems with taking the ota.
Click to expand...
Click to collapse
Who Unlocks Their Bootloader To Look At That Hidious Exclaimation Warning! Screen And Not Modify Their Device?
You State The Obvious.
Of Course You Blow Your O.T.A.'s..
And You Also Rush To Root... And Brick.. Based On How Many "HELP ME!" Threads Now Saturate The 7x Threads.
RaiderWill said:
Who Unlocks Their Bootloader To Look At That Hidious Exclaimation Warning! Screen And Not Modify Their Device?
You State The Obvious.
Of Course You Blow Your O.T.A.'s..
And You Also Rush To Root... And Brick.. Based On How Many "HELP ME!" Threads Now Saturate The 7x Threads.
Click to expand...
Click to collapse
I just got this device. I was on here seeing if theres a way to unlock bootloader and return to factory later. Because I knew the Oreo was coming soon. That's great news. I thought it was coming in May. So I'll just chill and wait for ota for now. Will honor come through when it comes to letting us unlock out bootloader that is the question. Or are they just working on updating a faster bootloader unlock process for us?
A Suggestion...
allrockedout said:
I just got this device. I was on here seeing if theres a way to unlock bootloader and return to factory later. Because I knew the Oreo was coming soon. That's great news. I thought it was coming in May. So I'll just chill and wait for ota for now. Will honor come through when it comes to letting us unlock out bootloader that is the question. Or are they just working on updating a faster bootloader unlock process for us?
Click to expand...
Click to collapse
Congrats On Purchasing A Fine Device...
LEAVE IT STOCK.
Take A Look Around The Threads..
Look at how many have bricked their 7x's
In Such A Hurry To Root... For What?
There Is Not A Stable Fully Functional Custom ROM Out There For The 7x.
There Are NO United States Of America FACTORY IMAGES Out There For The 7x.
You can eh.... Flash a Stock ROM from another country At Your Own Risk Of Course.
Have you stopped to ask yourself.. why Honor has not released Factory Images for this device.. that was announced in October of 2017 and released December 7th 2017 ?
People are actually PAYING services out there to recover their 7x's.... because they go down the rabbit hole and can't get out.
How Sad Is That...
You Were Wise To Stay Locked & Stock.. :good:
In about 60 hours you'll get your payoff..
Wait until Decryption is resolved before you Root.
Wait until a U.S.A. Factory Image is released before you Root.
You Can Do Everything With A STOCK 7x That You Can Do With A Rooted 7x
You don't need backups.... STOCK ROM'S DON'T CRASH... AND "FACTORY RESET IS YOUR BACKUP" when you don't root.
RaiderWill said:
Who Unlocks Their Bootloader To Look At That Hidious Exclaimation Warning! Screen And Not Modify Their Device?
You State The Obvious.
Of Course You Blow Your O.T.A.'s..
And You Also Rush To Root... And Brick.. Based On How Many "HELP ME!" Threads Now Saturate The 7x Threads.
Click to expand...
Click to collapse
I did, so I don't have to lose my data once factory images are available and I decide to root it in the future.
Yeah exactly the same reason as the post above mine. I unlocked the bootloader the day I got the phone so that way when the time comes to do any rooting or modding I wouldn't have to wipe my phone and lose everything. And I've still received all the ota updates on the L24 thus far with the unlocked bootloader.
RaiderWill said:
Congrats On Purchasing A Fine Device...
LEAVE IT STOCK.
Take A Look Around The Threads..
Look at how many have bricked their 7x's
In Such A Hurry To Root... For What?
There Is Not A Stable Fully Functional Custom ROM Out There For The 7x.
There Are NO United States Of America FACTORY IMAGES Out There For The 7x.
You can eh.... Flash a Stock ROM from another country At Your Own Risk Of Course.
Have you stopped to ask yourself.. why Honor has not released Factory Images for this device.. that was announced in October of 2017 and released December 7th 2017 ?
People are actually PAYING services out there to recover their 7x's.... because they go down the rabbit hole and can't get out.
How Sad Is That...
You Were Wise To Stay Locked & Stock.. :good:
In about 60 hours you'll get your payoff..
Wait until Decryption is resolved before you Root.
Wait until a U.S.A. Factory Image is released before you Root.
You Can Do Everything With A STOCK 7x That You Can Do With A Rooted 7x
You don't need backups.... STOCK ROM'S DON'T CRASH... AND "FACTORY RESET IS YOUR BACKUP" when you don't root.
Click to expand...
Click to collapse
Yeah but stock ROMs send your data to the Chinese government
str8stryk3r said:
Yeah exactly the same reason as the post above mine. I unlocked the bootloader the day I got the phone so that way when the time comes to do any rooting or modding I wouldn't have to wipe my phone and lose everything. And I've still received all the ota updates on the L24 thus far with the unlocked bootloader.
Click to expand...
Click to collapse
Still can't believe they took down the BL unlock site.
Sent from my BND-L24 using Tapatalk
I Fully Understand Your Reasoning..
EnIXmA said:
I did, so I don't have to lose my data once factory images are available and I decide to root it in the future.
Click to expand...
Click to collapse
It's A Logical Path To Pursue...
I have NO FAITH in Honor releasing Factory Images in the near future.
I think there is a "Method Behind The Madness"
Personally, my Android Data is all backed up in 2 places.. and it's all Android - Centric
I would NEVER do ANY personal business (Banking , Shopping Etc) on any Android device.
Especially an HUAWEI / HONOR device.. for all the reasons my Government has stated.
This is not a "Long-Term" solution phone for me personally.. It will be sold.. actually it would have already been sold, but I had $900.00 vehicle repair snatch my OnePlus 6 money right out of my hands..
This device was a Failure as far as gaining Developer support...
No Custom Kernels: "Franco's Kernel" oh if only... ( So why root.. You can't under / overvolt, swap governers, add features etc )
Even though Kernel Source was released 5 months ago.
It appears... Treble Ports are the way of the Future. I'm not complaining just stating facts.. ( I guess if I loved the 7x that much I would learn how to pack a Kernel for myself and use it..) but I don't love the 7x and it's Kirin Technology enough to do so.
This device will just never gain ground or love.. is hated by my government.. has the Un-popular ( For Developer's ) Kirin Processor and a weak GPu.
What it does have is Oreo 8.0 and Project Treble Support baked in.
Let's keep it shinny and in "Like-New" condition.. Pure Stock ( No Warning! Screens NEVER Modified in any way ) and ready to sell...
That's The Ticket.
So I'm unlocked rooted and running TWRP on my l24 does that mean I miss out on emui 8 or are there any Solutions
RaiderWill said:
It's A Logical Path To Pursue...
I have NO FAITH in Honor releasing Factory Images in the near future.
I think there is a "Method Behind The Madness"
Personally, my Android Data is all backed up in 2 places.. and it's all Android - Centric
I would NEVER do ANY personal business (Banking , Shopping Etc) on any Android device.
Especially an HUAWEI / HONOR device.. for all the reasons my Government has stated.
This is not a "Long-Term" solution phone for me personally.. It will be sold.. actually it would have already been sold, but I had $900.00 vehicle repair snatch my OnePlus 6 money right out of my hands..
This device was a Failure as far as gaining Developer support...
No Custom Kernels: "Franco's Kernel" oh if only... ( So why root.. You can't under / overvolt, swap governers, add features etc )
Even though Kernel Source was released 5 months ago.
It appears... Treble Ports are the way of the Future. I'm not complaining just stating facts.. ( I guess if I loved the 7x that much I would learn how to pack a Kernel for myself and use it..) but I don't love the 7x and it's Kirin Technology enough to do so.
This device will just never gain ground or love.. is hated by my government.. has the Un-popular ( For Developer's ) Kirin Processor and a weak GPu.
What it does have is Oreo 8.0 and Project Treble Support baked in.
Let's keep it shinny and in "Like-New" condition.. Pure Stock ( No Warning! Screens NEVER Modified in any way ) and ready to sell...
That's The Ticket.
Click to expand...
Click to collapse
How long you think it'll take for treble to be active for this device? I'm considering updating to the beta so I can then use the RR rom but whats the point if I can just wait a few days to get official Oreo and then be all in with treble. I guess I don't fully understand what treble is nor it's immediate relation to this device.
carnivalrejectq said:
How long you think it'll take for treble to be active for this device? I'm considering updating to the beta so I can then use the RR rom but whats the point if I can just wait a few days to get official Oreo and then be all in with treble. I guess I don't fully understand what treble is nor it's immediate relation to this device.
Click to expand...
Click to collapse
Treble will help get custom ROMs on our device faster. Just wait for official Oreo. Than we unlock bootloader. Wait for updated twrp with Oreo support. Than custom ROMs. Than would need treble support twrp. So we still have a ways to go for treble and custom ROMs. But we're getting close.
carnivalrejectq said:
How long you think it'll take for treble to be active for this device? I'm considering updating to the beta so I can then use the RR rom but whats the point if I can just wait a few days to get official Oreo and then be all in with treble. I guess I don't fully understand what treble is nor it's immediate relation to this device.
Click to expand...
Click to collapse
This is a simplified explanation of how Treble works, or at least my simple understanding of it. Google requires any device shipping with Oreo to have the main OS reside in its own partition separate from the OEM vender stuff.
Is no one else going to comment on how crazy this guy is?
Why Wait ?
carnivalrejectq said:
How long you think it'll take for treble to be active for this device? I'm considering updating to the beta so I can then use the RR rom but whats the point if I can just wait a few days to get official Oreo and then be all in with treble. I guess I don't fully understand what treble is nor it's immediate relation to this device.
Click to expand...
Click to collapse
Listen... You Don't Need To Wait For Anything...
I MAY BE 100% INCORRECT.. BUT, IT'S MY UNDERSTANDING THAT HUAWEI / HONOR HAS STOPPED THE ABILITY TO RETREIVE YOUR UNLOCK CODE (OFFICIALLY) FROM THEIR WEBSITE.
If True...
Do you know what that means?
It means... they MAY NOT enable the Vendor Partition in the OFFICIAL ( O.T.A. ) version of Oreo / EMUI 8.0 that will be released in about 48 hours from the time of this writing.
Without That Partition.... Project Treble is a NO GO.
In your case.. If all you want to do is run the ROM you mentioned, just use the Bootleg Method posted elsewhere in these threads to Unlock your bootloader.. Install one of these Unofficial TWRP's floating around... and install your ROM.
Done.
Why Wait?
For the Official Release of Oreo on Monday when all you are going to do is Overwrite it with a ROM posted elsewhere?
Sounds Like You Know What You Want...
Go For It.
Stock Oreo has NOTHING OF INTEREST for those that just want to flash Beta ROM's
Stock Oreo / EMUI 8.0 is for those of us that put 100% Stability and FULL Functionality First & Foremost..
I paid 100% of the Price for this Device.
I Personally.. Want 100% OF THE DEVICE'S SOFTWARE & FEATURES FUNCTIONAL...
At this point in the 7x's development... Only Stock EMUI provides that level of performance.
RaiderWill said:
Listen... You Don't Need To Wait For Anything...
I MAY BE 100% INCORRECT.. BUT, IT'S MY UNDERSTANDING THAT HUAWEI / HONOR HAS STOPPED THE ABILITY TO RETREIVE YOUR UNLOCK CODE (OFFICIALLY) FROM THEIR WEBSITE.
If True...
Do you know what that means?
It means... they MAY NOT enable the Vendor Partition in the OFFICIAL ( O.T.A. ) version of Oreo / EMUI 8.0 that will be released in about 48 hours from the time of this writing.
Without That Partition.... Project Treble is a NO GO.
In your case.. If all you want to do is run the ROM you mentioned, just use the Bootleg Method posted elsewhere in these threads to Unlock your bootloader.. Install one of these Unofficial TWRP's floating around... and install your ROM.
Done.
Why Wait?
For the Official Release of Oreo on Monday when all you are going to do is Overwrite it with a ROM posted elsewhere?
Sounds Like You Know What You Want...
Go For It.
Stock Oreo has NOTHING OF INTEREST for those that just want to flash Beta ROM's
Stock Oreo / EMUI 8.0 is for those of us that put 100% Stability and FULL Functionality First & Foremost..
I paid 100% of the Price for this Device.
I Personally.. Want 100% OF THE DEVICE'S SOFTWARE & FEATURES FUNCTIONAL...
At this point in the 7x's development... Only Stock EMUI provides that level of performance.
Click to expand...
Click to collapse
I actually like EMUI. I'm just concerned about the whole Chinese government thing mostly lol.
monorail0 said:
Is no one else going to comment on how crazy this guy is?
Click to expand...
Click to collapse
Haha yeah, and the extensive use of emojis really gets on the nerves.
carnivalrejectq said:
I actually like EMUI. I'm just concerned about the whole Chinese government thing mostly lol.
Click to expand...
Click to collapse
If I Handled My Personal Business On A Cell Phone... I'd Be Concerned Too...
If all you have are Android Apps.... who cares.
That's a PERSONAL CHOICE as to how much of your life you trust to divulge to your cellular devices.
And Yeah... as far as features an the ability to Customize a Pure Stock device, EMUI Kicks Ass and Takes Names :good:
And it's Soooooo Stable and Smooth.. and has 10 TIMES the Developer Support for Customization of what you ACTUALLY interact with.. than those who worry about what the Developer - Unfriendly Kirin Engine is doing.
It Cracks Me Up how many have went Ape S*it trying to Root and have bricked.. then are like OH MY GOD! HELP ME!
Leave the Damn thing "STOCK" until the day you have REAL REGIONAL FIRMWARE available to you.. To Fix Your Boo-Boos.. And leave all these BOOTLEG methods starting to pop up left and right alone.
ahmad.o said:
Haha yeah, and the extensive use of emojis really gets on the nerves.
Click to expand...
Click to collapse
Hey Ahmad...
Here is a way to avoid seeing my emo's
I ONLY POST IN "MY THREADS" WHEN IT COMES TO THE 7X... THERE IS NOTHING ELSE OF RELEVANCE HERE ANYMORE EVEN WORTHY OF MY TIME..
I'm sick of seeing " Help Me! My 7x has fallen and can't get up! " threads.
So you pretty much will not see RAIDERWILL & HIS EMO'S anywhere but in a thread he created.
SO AHMAD... JUST STAY AWAY FROM "A-N-Y" RAIDERWILL THREADS.... AND YOU'LL BE GOOD-TO-GO.
Why?
monorail0 said:
Is no one else going to comment on how crazy this guy is?
Click to expand...
Click to collapse
Monorail ? :laugh: You Have A Singular Wit.
If I'm insane.... Then Why Are You Reading The Comments Of A Madman?
Have You Asked Yourself that mono....
I Don't Know.... Over 1/2 of all the comments I've ever made on XDA have been "Thanked" for being useful or insightful.
But... since you're *Correct* in your assessment of RAIDERWILL... I guess the 500 or so others were either just as insane as RAIDERWILL for giving him Acknowledgment with a " Thanks! " or simply don't possess your keen insight...
Or... could it be that.. ANYONE on this rock we refer to as Earth.. that has the Unmitigated Gall to Disagree with YOU Monorail should be Hanged, Drawn and Quartered !!! :laugh:
Pssssst.... Hey You...... Over Here.. I'm going to tell you a secret to help ease your Ailment...
*Simply Don't Read RAIDERWILL'S COMMENTS OR THREADS..*
Done.
The are only a few roms that actually install but then some roms say they were flashed successfully but when i reboot the system it just bootloops.
I Currently have Slim Rom i'm pretty sure and it's 1 of the only roms that actually booted.
So if anyone can help that would be very helpful.
Baseband Version is M8992_1255331.29.01.88.09R
LGAGaming said:
The are only a few roms that actually install but then some roms say they were flashed successfully but when i reboot the system it just bootloops.
I Currently have Slim Rom i'm pretty sure and it's 1 of the only roms that actually booted.
So if anyone can help that would be very helpful.
Baseband Version is M8992_1255331.29.01.88.09R
Click to expand...
Click to collapse
You are running stock Nougat baseband. Most of the ROMs here were designed to work on the MM baseband so they will not work. Read through the forums here at XDA and you will see which ones you can effectively flash.
aybarrap1 said:
You are running stock Nougat baseband. Most of the ROMs here were designed to work on the MM baseband so they will not work. Read through the forums here at XDA and you will see which ones you can effectively flash.
Click to expand...
Click to collapse
Thanks I thought that it was the marshmallow as I seen a thread that said it was the marshmallow baseband
aybarrap1 said:
You are running stock Nougat baseband. Most of the ROMs here were designed to work on the MM baseband so they will not work. Read through the forums here at XDA and you will see which ones you can effectively flash.
Click to expand...
Click to collapse
Is there a way to get The Marshmallow BaseBand?
LGAGaming said:
Is there a way to get The Marshmallow BaseBand?
Click to expand...
Click to collapse
Not quite sure what's meant by your own meaning of Baseband. Your more than likely going to be answered by people still using the phone in different degrees of knowledge.
The experienced with a real practical application of this XT1575 device mostly have moved on to another device by now - but will any left on it be answering you. I'm glad to see @aybarrap1 has answered.
@stevejohnson42 uses the XT1575 too, and reports here and there of his flasholic tendencies on this device - might be helpful in any Nougat based ROM's to use the search box there and see if he's added anything in it.
Custom ROM Marshmallow development was always greater cause the XT1575 stayed on the Marshmallow OS for so long and because of Motorola not releasing Nougat sooner for it.
There are some Custom ROMS based on Nougat - just read their OP's to understand what's being required to using each one of them...
Nougat ROMs built for a Stock Nougat Kernel and Modem.
To answer your question without you going into a Blackhole in having to know more about your device in getting it back to good ground - I OFFER THIS-
Only way I know is to buy a XT1575 device that's never taken the servers Nougat OTA or has been ADB flashed to Nougat OS...
This as in ADB flashed questioned basically being understood by the device still having the bootloader status to LOCKED - as DEVICE LOCKED, the STATUS will still show 0, and it's software status of OFFICIAL.
Note: The Status Code will always show 2 = (relocked) or 3 = (unlocked), and it can never go back to 0 = (device locked), if it's ever been unlocked by a Motorola token code obtained from their site.
Otherwise you need an image of the Bootloader screen of the device up for sale.
THAT'S THE ONLY WAYS TO KNOW AND A SELLER SHOULD SUPPLY THIS AS A GUARANTEE AND/OR AN IMAGE SHOWING YOU FIRST...
OR YOU BUYING FROM A SITE AND ASKING THESE QUESTION OF THE XT1575 SELLER FIRST BEFORE THE PURCHASE AND THE SITE (LIKE EBAY) HAS A GUARANTEE IN THAT AD - TO FALL BACK ON...
To check this yourself-
1. Using (vol down + power button) put the device in bootloader mode where all of this is visible / should read as follows - see images also.
(A) - totally Stock non-rooted Marshmallow Baseband should read as - M8992_1255331.29.01.88.02R SUPER_NA
as taken from my Marshmallow XT1575 build MPHS24.49-18-16 devices Bootloader.
(B) - Shows the very same thing with device from the ABOUT PHONE in settings.
(C) - Rooted Custom Rom Nougat Baseband M8992_1255331.29.01.88.09R - from the ABOUT PHONE in settings / using the NuclearROM.
(D) - M8992_1255331.29.01.88.09R SUPER_NA - from the Bootloader Mode on same device - using the NuclearROM.
PS: I'm thinking, changing to a different Android build changes the Baseband build as well being applicable to the OS build version.
Warning:::
No don't ever do a complete ADB MM downgrade flash - if wanting to OTA back up to Nougat at some future point after already being on the Nougat OS.
To be clear "It's not recommended to downgrade" and allow a Moto X Pure device in taking the Nougat OTA again.
Once bootloader.img and gpt.bin are updated, there is no reverting back without the serious and the likely risk of a hard-bricked device. Only remedy at this time is a mainboard replacement. Confirmed in this threads post #75 .
A COUPLE POINTS - I'd like to make:
I've always clean flashed my XT1575 in custom roms and to going back in a stock Nougat OS - point being, I have never had any problems thereafter...
Another thing I'm thinking with an LOS based ROM - writes / changes some partitions parts that only with your ADB flashing back to the factory Official Stock Nougat can fix - changing everything back to an original partition structure.
- TWRP only backups a few partitions on the device, so partitions out of it's reach never gets restored back to an original stock environment with a TWRP backup when you do a restore using it/one made thereafter.
OTHER Reading you might want to do:
#30
#61
#73
#147
#179
#184
Baseband
I'm far from being a real practical experienced user in a XT1575 device but, I share in what I've taken a grasp of.
Hope this helps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LGAGaming said:
Is there a way to get The Marshmallow BaseBand?
Click to expand...
Click to collapse
Sorry I never got around to replying. @ResistanceIsFutile did a pretty good job explaining things as far as I can see. I just flashed stock Nougat within the last month with the intention of staying on stock rooted. I don't know if it is possible to downgrade any parts successfully but from what little I read a month ago on it, I did not remember anything staying how to do so.
LGAGaming said:
The are only a few roms that actually install but then some roms say they were flashed successfully but when i reboot the system it just bootloops.
I Currently have Slim Rom i'm pretty sure and it's 1 of the only roms that actually booted.
So if anyone can help that would be very helpful.
Baseband Version is M8992_1255331.29.01.88.09R
Click to expand...
Click to collapse
As @aybarrap1 has pointed out already, you are running a stock Nougat baseband,
Meaning you've also upgraded fully to the Nougat OS on your device.
Possibly, for someone new to the XT1575 on Nougat OS it's a good place to stay and get acquainted.
There's nothing wrong with Nougat. Root and TWRP are possible, as well advancing us further than what the Marshmallow OS offered.
I can understand Custom Rom wise, your wanting to "Is there a way to get The Marshmallow BaseBand?" but, consider that's just water under the bridge now - never to be the same for you. In anything you'd do to achieve this would just put your device in a Mixed-State, and where an advanced user would be better adapted of dealing with that.
That's why in my 1st. post to you I was trying to encourage you to read more, let it go awhile and sink-in, and read some more getting a mental picture as you understand the depth of everything related.
Or simply sell off your now XT1575 Nougat OS device and what to look for in a stock-locked bootloader of a Marshmallow OS XT1575 device and stay there not taking an OTA of Nougat.
Even in some Custom Rom's built for a Stock Nougat Kernel and Modem there have been changes related to the TWRP version needed to be used of them.
Here gives abit about that information.
I use the NucleaROM on one XT1575 and kind of bias towards it as I've stayed with it in my first flashing of a custom rom when OTAing up to Nougat that is after failing with LOS of the jumbled up thread for clark it uses.
[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Moto X Pure 2015 (clark)
Trying to decipher this LOS thread posts of Official versus Unofficial builds, versus using Modems of MM and Nougat and talking about LOS 14.1 and 15.1 builds along the way and all the different involved posts of each Official - Unofficial unlabeled subjects there of all the posts.
It's no place for an inexperienced user to go and easily understand it.
These are the posts https://forum.xda-developers.com/showpost.php?p=75763876&postcount=1303%22]https://forum.xda-developers.com/showpost.php?p=75763876&postcount=1303 that clearly pointed out the specific information in details that helped me to know of the differences to the posts while I was active in that thread.
I like the NucleaROM because it's being based on LOS, then I can and do - do it without Google for the most part. I've not flashed any g-apps what so ever, play store is not a concern for me to use - there are other less invasive places that don't have the requirements Googles PS imposes. (F-Droid)
Even running a root file explorer I don't see anything Google related - with the way I've installed NR
Besides running an apk through Virus Total gives me peace of mind.
Android is by Google and that's were G stops with me...
NucleaROM - (root - g-apps), all are optional for the two NucleaROM builds out.
Note:It's the wakeblock app or it's folder that is mandatory to do something with in NucleaROM.
In disabling it's app in phone settings (Apps) after 1st. boot, or removing it's folder in NucleaROM's root directory via TWRP before your very 1st boot into OS where you initially setup the OS.
Did any of this help?
aybarrap1 said:
I don't know if it is possible to downgrade any parts successfully but from what little I read a month ago on it, I did not remember anything staying how to do so.
Click to expand...
Click to collapse
Don't take this as Gospel and I don't advise it since we're Post Nougat now.
As it was Pre-Nougat - but, still don't hold me to it...
A stock firmware downgrade (in the terms of) Recovery, Kernel and OS may be performed without any noticeable adverse affects.
This was prior to Nougat, every OS update changes something with a deep impact.
So I'd advise you to check in whatever thread of a Custom Rom using Marshmallow base that your interested in. To finding out any facts before hand. Notably kernel and modem related THERE IN downgrading from Nougat to using it...
As too with what's been said - Once bootloader.img and gpt.bin are updated - there is no reverting them back (DOWNGRADING) without a serious likelihood in risk to having a hard-bricked device. You'd need to skip those parts in the downgrade commands used of your flashing sequence.
I have no real world practical application of experience doing this - just reading about it or book knowledge - that ain't squat to help in a time of trouble if that's what it yields...
ResistanceIsFutile said:
Don't take this as Gospel and I don't advise it since we're Post Nougat now.
As it was Pre-Nougat - but, still don't hold me to it...
A stock firmware downgrade (in the terms of) Recovery, Kernel and OS may be performed without any noticeable adverse affects.
This was prior to Nougat, every OS update changes something with a deep impact.
So I'd advise you to check in whatever thread of a Custom Rom using Marshmallow that your interested in. To finding out any facts before hand. Notably kernel and modem related THERE IN downgrading from Nougat to using it...
As too with what's been said - Once bootloader.img and gpt.bin are updated - there is no reverting them back (DOWNGRADING) without a serious likelihood in risking to having a hard-bricked device. You'd need to skip those parts in the downgrade commands of your flashing sequence.
I have no real world practical application of experience doing this - just reading about it or book knowledge - that ain't squat to help in a time of trouble if that's what it yields...
Click to expand...
Click to collapse
Thanks. As I mentioned earlier, I had planned on potentially using custom ROMs but I have decided to stay stock rooted. I just don't get that much into customization so a custom ROM just doesn't make sense for my purposes.
There's a change in the wind with Oreo...
aybarrap1 said:
Thanks. As I mentioned earlier, I had planned on potentially using custom ROMs but I have decided to stay stock rooted. I just don't get that much into customization so a custom ROM just doesn't make sense for my purposes.
Click to expand...
Click to collapse
Your happy with the stock Nougat - as I've said there's nothing wrong with it.
I get it and respect your decision to do just that in staying with a stock Nougat.
Custom ROMs aren't merely for customization's, back in the day especially with the array of cheaper devices it was the norm though. To make it in ones liking of a polished look or for performance enhancements.
The added themes and applications preinstalled by a manufacturer were reduced to almost nothing. This saved a lot of memory space and increased the device's performance, then with being able address the questionable UI design decisions that a manufacturer had made.
Besides with the XT1575 Moto X Pure, you needn't worry much about Motorola's manufacturers bloat and being skinned to something hideous and repulsive. By that, I mean your not dealing with and like the other manufacturers (tweaking Androids OS) add/remove/change the interface and apps to make it their own highly styled branded system.
Customization's was a way to truly make a phone your own and still is...
After installing a Custom ROM on Android you are the Admin of your Device which means no Objections, no Restrictions, and basically nothing hampering you as your free to do anything with your Android device.
But, customization's is only one facet in the equation to consider with a custom rom.
Taking a view of all devices in the realm of Custom ROM's offered to each (not just an MXP), there's something more also to be gained.
Updates:
One of the most frustrating things about owning an Android device is waiting for your manufacturer to push an update to your phone, so you can get the latest features. The newer versions of Android are not only interesting because they bring new features but, also because they fill security gaps.
Often times manufacturers will even cut support for your device entirely (thinking of Motorola's support for the MXP). This leaves you stuck with a phone on an older version of Android and less secure. The solution is a custom ROM on the newest or a newer Android version for it.
Privacy and Security:
The recent alarming News surrounding data collected by OnePlus devices (along with a second claim that the company has denied), having highlighted the amount of trust we have to place in our phones by the manufacturer itself now.
This doesn't apply more to budget phones in that they may have security problems. And even the world’s second largest smartphone manufacturer, Huawei, has recently found its US ambitions blocked by US security agencies over concerns about it's spying.
And even once you get past this, every Android user is handing over vast amounts of personal data to Google and others (App's) every single day.
[[Like I pointed out in post #7, I like the NucleaROM because it's being based on LOS, then I can and do - do it without Google for the most part. I've not flashed any g-apps what so ever.]]
Lineage OS has numerous privacy controls built in, including a Privacy Guard that restricts how apps can use your data. Plus, you can use it without Google apps if you prefer !
A custom ROM can help address your security and privacy concerns. ROMs are, or should be open source. The code is available for anyone to scrutinize. Even if you don’t have the skills to analyze it yourself, you can be assured someone will flag any privacy concerns to it's custom rom using community.
Other Benefits:
Then one can benefit possibly with Performance, Battery Life. In some cases, you might even be able to unlock new functions or find features from newer flagships ported back to older devices. These are the types of phones that rarely get updated, and are often not as well optimized as their higher end siblings.
Disadvantages:
Sure Custom ROMs have their own, it's not going to be a sunny days walk in the park everyday. Expect some rain too, like in adding an app, tweaking hidden settings of the Android's OS and like-
"many phone cameras have dual lens setups nowadays, fancy HDR effects, and high frame rate 4K video. They all need special tools to drive them, and these are all part of the phone’s manufacturers firmware. There’s no one app that you can simply lift and install on another device. Nor can you replace all of the cameras functionality with a third-party camera app."
Closing thoughts:
One of the biggest draws of custom ROMs used to be that you could install the stock Android experience on any device. You could replace the bloated software from Samsung, Huawei, or HTC and other manufacturers with a ROM based on the open source version of Android. Throw in the suite of Google apps, and you’d have something akin to a pure Android device. This is the principle around which Google’s Nexus phones were built. {In reality, Android is but one of the parts of your phone's software today, not the total sum of those parts as manufacturers hardware needs it's own drivers to function.}
But, that makes the stock Android no longer the best version of Android, even Google admits this. The best parts of the company’s Pixel phones aren’t Android. The camera app, Google Assistant, and the fast streamlined launcher are all proprietary software. They’re developed and owned by Google. In fact, on the product pages for the Pixel phones, Android barely even gets a mention there.
Custom ROMs can be wonderful for older devices but, before you decide to change your device's original manufacturers firmware you should familiarize yourself with the disadvantages of the process.
Custom ROMs are perfect for those who love a good challenge. But if this doesn't sound like you then you won't like custom ROMs. Between the devices need for security updates that custom roms can offer. Comes a need to unlock the bootloader, install a custom recovery, gain system root and dealing with unstable versions being pushed to a device, and having an active ROM maintainer.
Those are some of the things where your patience could reach its limits fast.
Not forgetting, third-party firmware (as in custom roms) comes with very few or no Google apps. The Play Store application has to be installed again if you use that source for you add-on apps.
Then hardware specific software (drivers) to make a devices hardware function properly.
So is it Your device because you've paid for it, or is it a manufacturers device with their own branded apps, style and the flair they choose for you of the price you've paid for it.
It's Your choice and decision to change it or not... :good:
PS: Devices that started to ship with OREO installed will change the custom rom landscape.
There's a change in the wind with Oreo...
Project Treble has some interesting implications for the revival of the custom ROM scene.
XDA community members are excited about the prospect that we may be edging closer to a time where Android software can be easily ported across a range of devices.
Other developers have also already shown off a single system image capable of booting on different devices with different processors.
ResistanceIsFutile said:
Not quite sure what's meant by your own meaning of Baseband. Your more than likely going to be answered by people still using the phone in different degrees of knowledge.
The experienced with a real practical application of this XT1575 device mostly have moved on to another device by now - but will any left on it be answering you. I'm glad to see @aybarrap1 has answered.
@stevejohnson42 uses the XT1575 too, and reports here and there of his flasholic tendencies on this device - might be helpful in any Nougat based ROM's to use the search box there and see if he's added anything in it.
Custom ROM Marshmallow development was always greater cause the XT1575 stayed on the Marshmallow OS for so long and because of Motorola not releasing Nougat sooner for it.
There are some Custom ROMS based on Nougat - just read their OP's to understand what's being required to using each one of them...
Nougat ROMs built for a Stock Nougat Kernel and Modem.
Click to expand...
Click to collapse
Not much to add - I share @ResistanceIsFutile comment - once you have updated - don't try to go back to earlier modem / baseband on this phone
Here is another collection that gives you choices and very clear which version to use for
https://forum.xda-developers.com/moto-x-style/development/collection-random-projects-t3662970
Personally - I flashed the stock ROM that is here ( make sure you have correct variant before doing ) :
https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
to move from Marshmellow modem - as noted above ; much more development on the original modem -- but I had a nagging issue with the Fly Delta app that could be duplicated but not something developers of custom ROMs should have spent time on - going to Nougat stock cleared it - then I went to NucleaROM almost immediately and everything worked fine
I have never tried - but , by searching xda-- you will find many active developers noting it is a good way to brick the phone .. I do not pretend to fully understand -- but have learned long ago to do research , carefully read OPs and safest to follow instructions of those who have much greater knowledge than me .
The phone is still my daily driver - I am currently on rooted stock that was installed by the method noted in the thread above. I have been on NucleaROM as DD and a good ROM ..and have flashed many posted by obsolete1. I have found with many back to back clean flashes - reflashing stock can eliminate issues that you might run into ( don't remember them all - but do recall having an issue wiping phone once )
Also - check carefully what TWRP to use - some of the ones using the Nougat modem require the unofficial TWRP that Hashbang developed for the earliest ROMs that worked on it.
We had a pretty good run on this phone and it appears there still might be a few developers looking at it .. but I understand ; most of them have moved on to other phones or the reality of life has required them to leave development for awhile
Regards
@ResistanceIsFutile
Thanks for the run down and I'm quite aware of many of these things. The MXPE in itself is a great phone with the few added features for Moto being actually somewhat useful.
I am not overly concerned with updates. If I were I would get a pixel or Android one phone.
Prior to the MXPE I had carrier branded phones and found custom ROMs to be quite useful in terms of bloat and better performance.
@aybarrap1
Only meant it peaceably - didn't mean by steps on any toes or persuade - crowd you or anyone at all.
The Moto X style/pure devices age has probably 3rd, 4th even 5th generation owners by now that have no ideal what we're talking about at times.
I then see it as a funneling effect, when I answer one it spreads out to others not knowing, especially in a threads topic as this. If you prefer I'll answer generally and not address anymore to you - I'm easy and would like to make friends on XDA - not loose any prospects.
I like and see your posts as helpful as I hope mine are, and it's encouraged to answer if you can at any experience level on XDA. So please forgive any misunderstanding or intentions on my part.
Thank you.
Everything is beneficial but not useful to all
@ResistanceIsFutile
Thanks. Reading back I see how the "tone" came across. I'm good and only intended to put out my reasons. I do have to say it is good you post this info as it was posts like yours that helped me a lot when I first started looking into rooting and custom ROMs some many years ago (LOL...7 or 8 years only but in terms of phone tech that is a very long time).