i've been sitting on the first pie release since... november? at the time i figured i'd just flash new FTFs as they turned up on xpericheck but now i've realised they're all hosted behind a paywall. and i've seen @j4nn's [XZ1c] rooted kernel hiding bootloader unlock with working fota thread but there isn't a kernel there for my particular build. so just wondering what everyone's approach has been since rooting became a possibility? are firmware files hosted anywhere else?
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Related
I have been rooting, unlocking, and loading Roms on other devices for awhile now, but I'm not familiar with how to manage stock updates. I can't seem to find anything, (so maybe this info could be added to a sticky).
I'm rooted with TWRP and a zipped OTA has been posted in anothet thread for my device, XT1064. What can I do to load it? Do I need to flash back to stock first? Can I simply run a fastboot command? I feel like I should know this by now but I'm a bit confused by all the different sources of information.
Thanks, all, for your help.
I have the same question. If someone who has done this, is out there, please let us know.
you tried asked in that other thread???
If is the OTA update do not use it!!!
If you received the OTA on your phone do not update!!!
you will brick your phone.
To install OTA revert back to stock with the factory image. You will go back to Stock Kernel and recovery.
Or wait til someone builds a stock updated ROM and flash that.
If is a image of the ROM, not the OTA, a already updated ROM just follow the instructions on the thread...
Yes, I did ask in the other thread, but I thought it would be better to post a new Q&A thread to keep from cluttering up the other one. Thanks for your help. I'll just wait for a flashable ROM..
Try this method:
http://forum.xda-developers.com/moto-g-2014/help/guide-update-to-lollipop-losing-apps-t2979971
The main idea with OTA is the incremental nature of the update. To keep OTA filesize to a minimum, the system will be patched, not completely overwritten.
So, if you have altered your system in any way, OTA will fail, because it tries to patch files that differ from what it expects. The OTA will check which device it is executed on and will perform various checksum tests before actually installing itself.
If you are experienced with flashing and know how to modify the update-script inside the OTA.zip, then you can go from XT1068-4.4 to XT1064-5.0.1.
But it is quite a lengthy process and not easy nor recommended
You have to go from XT1068-4.4 to XT1064-4.4 to 5.0 to 5.0.1 and must restore the modem. Last but not least the build.prob has to be modified to reflect dual-sim capability.
By the way, the need to lock the bootloader for OTA is a myth. It is not necessary.
Hello All,
I've just flashed the AOSP ROM for THEA XT1072 and I'm very happy with the results, it's exactly the return to stock I was looking for. However, I have a few questions I hope somebody can kindly answer:
1) Is it possible to re-lock the bootloader once an unofficial ROM has been installed? My device is telling me I need an officially signed ROM and refusing to relock when I do "mfastboot oem lock".
2) What's the update process for installing later builds of the AOSP ROM? Is it just a case of checking back here and re-flashing the whole new image as and when it is released? Or is there an OTA update alternative?
3) Is the current AOSP build 20150828 inclusive of the various security fixes that Google rolled out recently (Stagefright etc.)? I know they were released to AOSP source code but that presumably doesn't guarantee they are in the current THEA 20150828 AOSP build yet.
Thanks
sharkyblunt
sharkyblunt said:
Hello All,
I've just flashed the AOSP ROM for THEA XT1072 and I'm very happy with the results, it's exactly the return to stock I was looking for. However, I have a few questions I hope somebody can kindly answer:
1) Is it possible to re-lock the bootloader once an unofficial ROM has been installed? My device is telling me I need an officially signed ROM and refusing to relock when I do "mfastboot oem lock".
2) What's the update process for installing later builds of the AOSP ROM? Is it just a case of checking back here and re-flashing the whole new image as and when it is released? Or is there an OTA update alternative?
3) Is the current AOSP build 20150828 inclusive of the various security fixes that Google rolled out recently (Stagefright etc.)? I know they were released to AOSP source code but that presumably doesn't guarantee they are in the current THEA 20150828 AOSP build yet.
Thanks
sharkyblunt
Click to expand...
Click to collapse
1. No.
2. Just flash rom without any wipes as there's no OTA functionality.
3. Yes.
Thanks Luk. Great work on this ROM. It flies compared to the stock 5.0.2 and no issues yet.
Only one issue so far, after 24 hours of using it. I'm getting a battery drain whereby Miscellaneous is by far the biggest culprit (currently at 22% since taking it off charge this morning). It was the same yesterday too, and I rebooted it last night just in case it was a hangover from the original flashing, but it's still draining faster than stock 5.0.2 did.
The AOSP-5.1.1-20150905 build is perfect (once I'd erased the modemst1 & modemst2 to get GPS working). No issues whatsoever from me. Great work.
By the way, I'm commenting here as I've not done enough posts to participate in the developers sub-forum.
Alright, we need to stir the scene up... and God is it past the due time.
Blu has had the Kernel sources available in their ftp server since August IIRC and the Gionee equivalent of this phone has been running Marshmallow for more or less the same time.
So here's my github with the kernel sources on it: https://github.com/batoussai/android_kernel_VivoXL
I fixed the problems I found with improper makefile prepending and inclusions in headers and c files. It compiles successfully but so far I haven't had time to test if the phone works with it flashed, and I really need some sleep now.
What needs to be done now is:
-Get a reliable way to unlock the bootloader.
-Test the kernel as it is now.
-Start development of modified kernels.
-Think of what should be done afterwards.
Anyone and everyone is more than welcome to help (specially since I'm mediocre dev and things will take forever with only me working)
Reserved
you mention getting the bootloader unlocked, but is that only to get TWRP on there or allow kernel changes? i have TWRP, supersu, but still have a locked bootloader... I have been wanting to make some real changes on this phone
stonerphoner said:
you mention getting the bootloader unlocked, but is that only to get TWRP on there or allow kernel changes? i have TWRP, supersu, but still have a locked bootloader... I have been wanting to make some real changes on this phone
Click to expand...
Click to collapse
I'm not sure you will be able to edit the kernel partition with a locked bootloader.
My phone decided that it would accept having the bootloader unlocked now and I don't really want to test relocking it.
And in other news, the compiled kernel works as supposed and my phone still boots after flashing it (had to repack the ramdisk from the stock kernel to make the boot.img)
let's try it for variant condor pgn-605 p8 the same as blu vivo xl but bootloader is already unlocked
i have bootloader unlocked i hope i can test it with rom like cm 13 as soon as one of you can make it for us
https://atozhacks.blogspot.com/2016/10/rommmhios-rom-for-gionee-splus-by-splus.html
i found this rom work perfectly
This might might provide some pretty useful references for me. Thanks @mwalid25!
And updating a bit, currently working on the device tree and proper ramdisk generation. As soon as I get results I'll upload it to github too.
Also, if anyone wants to help pester Blu into releasing the stock firmware too, that'd be appreciated since currently we depend on third party stock releases that I can't attest the integrity since I didn't bother comparing them to my stock firmware while I could.
Hello,
first: sorry if my question feels too casual.
Current case:
I own a P10, unrooted, unmodified bootloader/systemfiles, currently running on L09C02B161, which should be the last patch level before Oreo. According to firmware finder, the newest build is L09C02B374 (FullOTA-MF-PV). But that one is not flagged available to my phone*.
Planned:
Pretty much the full gameshow. I wanted the officially signed update to Oreo to have a stable boilerplate, then add twrp, root, xposed, magisk, xprivacy, get rid of the bloat,... Lots of topics not to be discussed here (and I'll do my homework on them all before even asking about it). Summing it up I'll mod the os anyway.
Having that in mind, is it a good idea to wait for that system update to become available for my device at all? Any upsides? Maybe the manual update or twrp installers are unstable or risky, or maybe I'll lock myself out from OTA's, or anything? I'm generally not an impatient person, but reading about Oreo for the P10 since late 2017 and not getting my hands on it kinda nagged me up to a point that I want to evaluate my options now.
*Screenshots of System Updater and Firmware Finder: imgur.com/a/6wbJA
So I'm looking into a bunch of the firmware builds and OTA updates. And what I've found, is that I have a 5DSC1 kernel signed with test keys. And I also have this same kernel signed with release keys.
Same actual debug kernel, but two copies signed with two different keys. Something seems different with the 5DSC1 build.
And it isn't even the first 5D BL rev. Those pie betas were the first builds to use the 5D BL back in December. But they kept putting out 5C BL builds to the public until March.
Anyone else have some insights here while I continue diving down this rabbit hole?
Because while we can't directly access our recovery logs, you can still view them in recovery mode. And looking at the log when OTA updating to 5DSC1 gives a lot of information for using the FOTA tools.