Folks,
This is something we should keep an eye on:
FXP article: "Finally! Boot to recovery enabled in special bootloaders from Sony"
=> http://fxpblog.co/2015/05/01/finally-boot-to-recovery-enabled-in-special-bootloaders-from-sony.html
Let's hope there will be a Z3c open bootloader in the works.
arturiu said:
Folks,
This is something we should keep an eye on:
FXP article: "Finally! Boot to recovery enabled in special bootloaders from Sony"
=> http://fxpblog.co/2015/05/01/finally-boot-to-recovery-enabled-in-special-bootloaders-from-sony.html
Let's hope there will be a Z3c open bootloader in the works.
Click to expand...
Click to collapse
While coming from an Nexus 4 and waiting for my Z3C delivery to arrive.
I just read that bootloader news, too. Would it be useful to wait some time, if Sony releases some updated bootloader?
Or perhaps better to say, are there any huge problems / differences with the current procedure of unlocking the Z3C?
I already noticed the list for unlocking and rooting is very long with respect to N4 ....
damaddy said:
While coming from an Nexus 4 and waiting for my Z3C delivery to arrive.
I just read that bootloader news, too. Would it be useful to wait some time, if Sony releases some updated bootloader?
Or perhaps better to say, are there any huge problems / differences with the current procedure of unlocking the Z3C?
I already noticed the list for unlocking and rooting is very long with respect to N4 ....
Click to expand...
Click to collapse
The "unofficial" method of installing a bootloader is currently stable, thanks to many xda contributors (check this same forum for it).
But it's not officially supported by Sony and it involves a step that invalidates the device DRM keys.
You can (and should) perform a backup of the TA partition in order to restore those keys if you want to revert to an official firmware.
What is announced there may take some time for the Z3c, and it's not guaranteed to happen. But it would certainly make things easier...
So if you want to test a different rom, you should go with the current process.
(important: do some research on this same forum, follow the instructions, and start by backing up)
As to the device itself, you won't find a gadget out there comparable in specs and size.
IMHO, it's a default choice for a compact high-end device.
are there any news about the bootloaders?
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.
Many devices tend to loose picture quality when unlocked, it never happened to me with my previous devices but I need to ask to users here if it will happen with the g4 plus,
I am talking about the picture quality in stock ROM here, will an unlocked bootloader affect the picture quality of stock ROM?
Sent from my Moto G (4) using Tapatalk
Unlocking the bootloader does nothing (zero changes) to the actual system files. It won't affect the "quality" of pictures.
The only time when, after unlocking, picture quality decrease is when using a ROM/firmware that doesn't integrate the correct blobs for camera or the native app - this is the case with some (most) CM/Lineage ROMs.
Unlocking the bootloader will not affect the picture quality. Changing ROMs can affect picture quality though , depending on the libraries and the camera app. I faced the same issue initially, but eventually it got better.
Thanks for your answers ?
Couple of questions
1. Is the 22/5 build of LOS stable, means is everything working?
2. Can I relock bootloader and reclaim warranty?
Sent from my Moto G (4) using Tapatalk
Haven't tried LOS but as far as the second question is concerned, it's better you keep your bootloader unlocked since problems may arise with locked bootloader and custom ROM, and AFAIK you cannot flash any custom file with a locked bootloader. Plus you won't gain much by locking your bootloader...(correct me if I have stated anything wrong)
pooniaprashant said:
Thanks for your answers
Couple of questions
1. Is the 22/5 build of LOS stable, means is everything working?
2. Can I relock bootloader and reclaim warranty?
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
In addition to what nlp931 has mentioned, re-locking your bootloader will not recover your warranty. Motorola has a record of the unlocking and thus voiding of the warranty - there are reports of some users re-locking their devices and being able to claim warranty repairs. How much of that was up to the discretion of the service centre, the repair performed or simply looking at the receipts (rather than checking the IMEI), I don't know. Also, relocking (and unlocking again) may wipe your device.
I concur though that re-locking a bootloader is only advisable with stock firmware - given the verification checks performed at boot, having anything custom (be it recovery, system or kernel) may trip those checks and render your device unable to boot!
Having a quick look through the posts around the 22/05 LineageOS release, looks like there's not much in the way of bugs (call recording isn't working still, it seems) and Moto camera won't work without deleting of .jar files (or you could flash the patched camera app https://forum.xda-developers.com/moto-g4-plus/themes/stock-motorola-camera-t3596659). Additionally, as mentioned above in the thread, the camera quality may be subjectively different to stock. If you're looking to theme LineageOS, there's the OMS version too with Substratum support: https://forum.xda-developers.com/moto-g4-plus/development/unofficial-lineageoms-14-1-athene-t3598237 I don't think the OMS and official builds are compatible with each other though (on a side note, the OMS build is newer than the official build at the moment )
Oh, as with any custom ROM, if you've got a G4 Plus, ensure you've updated to Nougat before flashing the custom ROM, else you're likely to run into fingerprint enrolment issues....
1. When you unlock the bootloader, you provide the serial to Lenovo in exchange for the unlock code. And you will click on a agreement that says that you will loose the warranty. They keep that record on their servers, re-locking will not erase that.
2. With any LOS firmware you will have issues with camera, the drivers for that are proprietary, you are stuck using generic drivers.
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.