Related
After spending the last few days trying to build AOSP 6.0 from source, I finally got it to compile. I have links to the system.img, boot.img, recovery.img, and userdata.img if anyone wants to try it out.
Edit: Files removed. If anyone wants to test out AOSP 6.0 for the Z5, look through the thread. zacharias.maladroit got it to work.
hi
i want to try it but just tell us what's working and what not?
RIL, Camera, Video playback, sensors, fingerprint ?
lonely2k5 said:
hi
i want to try it but just tell us what's working and what not?
RIL, Camera, Video playback, sensors, fingerprint ?
Click to expand...
Click to collapse
Sorry, I don't know what works and what doesn't. This is built straight from Sony's aosp build guide. It probably is not stable. I just thought that some people might want to test it out, seeing as there are no marshmallow builds on the internet.
ok
so you haven't even tried if it boots?
i'll try and see what happens..
is the build with all changes as z3 concept?
i had no time and didn't follow the aosp some time...tried to build it when it came out but not sucseeded...
lonely2k5 said:
ok
so you haven't even tried if it boots?
i'll try and see what happens..
is the build with all changes as z3 concept?
i had no time and didn't follow the aosp some time...tried to build it when it came out but not sucseeded...
Click to expand...
Click to collapse
When I tried to build it with the guide given, I ran into an issue saying "fatal error: pm-service.h: No such file or directory". Someone else had this issue too, and it was suggested to use this patch: https://android-review.googlesource.com/#/c/180351/. Once I did that, the build succeeded. I have not yet tested it out.
i'm flashing it now...but sending system.img is taking cca 10min now..we'll see..
p.s. looks like something is wrong with system.img...other parts flash ok but cannot flash system, it freezes and have to abort it
lonely2k5 said:
i'm flashing it now...but sending system.img is taking cca 10min now..we'll see..
p.s. looks like something is wrong with system.img...other parts flash ok but cannot flash system, it freezes and have to abort it
Click to expand...
Click to collapse
Try this command instead. This is what Sony recommended in their guide:
fastboot -S 256M flash system system.img
thnx
worked...
booting now...i'll report
1st boot
- some screen flickering and artifacts on booting screen...
- bootloop
2nd boot
same as 1st boot...
lonely2k5 said:
thnx
worked...
booting now...i'll report
1st boot
- some screen flickering and artifacts on booting screen...
- bootloop
2nd boot
same as 1st boot...
Click to expand...
Click to collapse
Darn that's disappointing. I'm gonna try to recompile it and see if it works this time.
ok
should i wait?
how long will it take?
lonely2k5 said:
ok
should i wait?
how long will it take?
Click to expand...
Click to collapse
It'll probably be a few hours. I will update my post as soon as I finish. Let's hope it works.
lonely2k5 said:
ok
should i wait?
how long will it take?
Click to expand...
Click to collapse
Okay, I updated the original post with the new files.
sorry but not working...
it looks like it's not bootloop as it stays connected to flashtool all the time but boot animation going for ever...
flashtool recognizes it ok
---
22/054/2015 08:54:53 - INFO - Connected device : Sony Xperia Z5
22/054/2015 08:54:53 - INFO - Installed version of busybox : N/A
22/054/2015 08:54:53 - INFO - Android version : 6.0 / kernel version : 3.10.49-perf-g6187ade-dirty / Build number : MRA58K
22/054/2015 08:54:53 - INFO - Checking root access
22/054/2015 08:54:54 - INFO - Root access denied
---
@Uclydde Your Latest AOSP-M Build boot's up but it has artifacts on boot, it does optimize apps, will report back and test everything out.
EDIT: I don't know why but the app-optimizing-process takes very long, maybe because i did a dirty flash to keep userdata from prevouis Stock-Xperia-Firmware.
Best Regard's
Alex1911
@Alex1911 how long did 1st boot took for you? mine was 20min and still not optimizing apps...
lonely2k5 said:
@Alex1911 how long did 1st boot took for you? mine was 20min and still not optimizing apps...
Click to expand...
Click to collapse
the optimizing about 20 min. then i was like it would boot but it didn't, it crashed (blinking red led) and then rebootet
Best Regard's
Alex1911
i had this when i flashed stock rom without checking to delete userdata when going back to 5.1.1
had to reflash with delete userdata checked and then it was ok
maybe here it's only userdata.img problem
hi
any plans of a new build? any improvements or changes found to make it bootable?
thanx
Uclydde said:
After spending the last few days trying to build AOSP 6.0 from source, I finally got it to compile. I have links to the system.img, boot.img, recovery.img, and userdata.img if anyone wants to try it out.
system.img: https://goo.gl/w3AqVx
boot.img: https://goo.gl/PqmrdH
userdata.img: https://goo.gl/YqVriX
recovery.img: https://goo.gl/IrVSFg
Edit: I recompiled after the first one didn't work. Here are the files:
system.img: https://goo.gl/lZIqRu
recovery.img: https://goo.gl/krPWQj
userdata.img: https://goo.gl/SAlsgE
boot.img: https://goo.gl/tlcLVp
Click to expand...
Click to collapse
I have compiled and successfully booted into aosp marshmallow as well as lollipop two days ago.
However here's what's interesting, since there isn't a specific way to install a custom recovery for the marshmallow, there is no way to install gapps! Also, mobile networks as well as sd card doesn't work! Only WiFi works. As for the lollipop, after using the dirty root method, I could install gapps. Also mobile networks work, but the sd card functionality is still missing. And camera fails to work in both the aosp builds.
To summarise what doesn't work:
AOSP_L_kitakami_sumire:
Not working - sd card, camera.
AOSP_M_kitakami_sumire:
Not working - mobile network, sd card, camera, gapps.
P.S.: I can upload the image file links if anybody is interested in flashing it! But I still see no point in doing so unless you're interested in testing out a few apps that you're designing specific to this device.
Cheers.
@Uclydde
hi, is there any progress for AOSP M ?
Best Regard's
Alex1911
Because having my old reliable daily driver gathering dust really bothered me for too long...
This is a plain build of LineageOS 13.0 with the xt926 target. Pretty much everything necessary to build it is already in git, it just doesn't have any official builds or any official LineageOS maintainers. It's an opportunity for someone who still loves this device... I'm going to try to get 14.1 working and hopefully turn this over to someone who has the time to become a LineageOS maintainer for the device.
It requires KitKat bootloader. Your bootloader should also be unlocked (e.g. with Motopocalypse).
This is also my first time building Android and actually using it, so if you think I should have done something differently, feel free to let me know! I've been lurking on XDA for many years and I've learned a lot. This is the first chance I've had to start giving something back.
How I built it
I built this using LineageOS build instructions, just substituted xt926 as the build target and cm-13.0 as the branch. I had to replace external/tinycompress/ because it wouldn't compile; I used upstream Google sources, then it compiled properly.
I pulled missing proprietary blobs from https://github.com/TheMuppets/proprietary_vendor_motorola from the cm-13.0 branch.
Questions
What about LineageOS 14.1?
I plan to attempt to build 14.1 next. But unlike 13.0 it doesn't already have an xt926 build target defined so it's going to take some extra work. If all goes well, I'll be able to post builds in the next few days. If not...
Why don't you support JBBL?
Because it would be a lot of extra work. And from the preliminary look I've taken, it seems that 14.1 will probably require KKBL anyway, and not work at all with JBBL.
Does it work on xt907/xt925?
It should do. I don't have either of these devices so I can't test it and I can't guarantee it. But you can always try it!
Does it work on other phones?
If it's msm8960, then maybe. Otherwise, probably not. But feel free to brick your phone if you really want.
Download
System: lineage-13.0-20170706-UNOFFICIAL-xt926.zip
Recovery: lineage-13.0-20170706-UNOFFICIAL-xt926-recovery.img
Instructions:
Flash recovery from fastboot (optional). You can use the included recovery or some other recovery you already have.
Flash system ZIP from recovery. Flash gapps at the same time before rebooting out of recovery.
Wipe data/cache.
Reboot system and Enjoy!
I'm really interested in flashing lineageOS to my Droid RAZR HD devices. Unfortunately, I think these specs are incompatible:
* System Version: 182.46.15 XT926 Verizon.en.US
* Model Number: DROID RAZR HD
* Android Version: 4.4.2
* Baseband Version: VANQUINSH_BP_100731_020.64.21P
* Kernel Version: 3.4.42-gbd361ac
* Build Number: KDA20.62-15
* Build Date: Tue Jul 29 02:51:09 PDT 2014
Without going through all the tr.apk/motopacalypse.apk stuff, do you know of any way to make this happen? thanks.
I'm really interested in flashing lineageOS to my Droid RAZR HD . Any bugs? thx
Thanks for posting this! I tried installing it on my unlocked Verizon XT926, and got stuck at the animated logo in the boot sequence. I had the same problem with the CM11 M2 snapshot, but CM 12.1 works.
In both cases, I tried wiping data, cache, Dalvik cache, and system multiple times; I reinstalled and re-wiped in different sequences and combinations. (All operations were in TWRP.) I also tried cold booting and booting with and without SIM and SD card. I did not attempt to install GApps.
Bootloader version: 10.9B
Baseband version: VANQUINSH_BP_100731_020.64.21P
pentaflox said:
Thanks for posting this! I tried installing it on my unlocked Verizon XT926, and got stuck at the animated logo in the boot sequence. I had the same problem with the CM11 M2 snapshot, but CM 12.1 works.
In both cases, I tried wiping data, cache, Dalvik cache, and system multiple times; I reinstalled and re-wiped in different sequences and combinations. (All operations were in TWRP.) I also tried cold booting and booting with and without SIM and SD card. I did not attempt to install GApps.
Bootloader version: 10.9B
Baseband version: VANQUINSH_BP_100731_020.64.21P
Click to expand...
Click to collapse
I've had this issue in the past. First wipe your system, I usually do a format data as well (you will lose everything on your internal SD if you do this, external SD should be fine). Install CM 11, reboot to recovery, don't wipe and dirty flash whatever CM/LOS rom you want.
Ok, so I said all of that, and then got stuck for forever. I couldn't use my copy of TWRP 2.8.6.0, I had to use the recovery posted in this thread. I then did a factory reset (full wipe) and was able to install this build and get it to load.
I'd love to see an updated TWRP for KBBL, but I don't think we'll ever get that.
---------- Post added at 01:38 PM ---------- Previous post was at 12:58 PM ----------
Triple posting here:
I got into the system and things ran...ok. I rebooted to recovery and installed the latest opengapps pico package and everything went wrong. The device is now running very slowly and I can't log in to Google. It looks like it's going to work, but sits at "Checking info" for a long time before saying I can't log in. Comparatively, running the JBBL, Photon Q recovery, and latest official Lineage build for the Photon Q works much faster and without issue. I don't like running JBBL, and would rather have a build for my device and not a similar one, but that may be what I need to go back to.
I just tried another flash without rebooting between rom and Gapps and I'm getting stuck at the same point.
Another update:
Just tried opengapps nano package, I was able to get through the sign-in process with this one, but it's running slower with this package than with the pico. I'll give it a try for a couple of days and will try to remember to stop back to leave more feedback. I still need to test voice calls, since they don't work with the photon q (speakerphone works but not the built-in mic)
Well, no audio works. I can't play back local audio, both mic and earpiece are dead, no loudspeaker or speaker phone mic either. Back to 12.1 for now. I'll keep an eye on this thread too. Thanks!
why dont use the LOS13 for de xt 907? that rom runs very well in xt925 with jbbl. All is functional.
@error28, can you submit your work to a LOS branch so that others can commit changes, too? I retried installing this build today using the recovery you linked. Even though some things don't work, this seems like a great start and it would be terrific if it attracted more contributions.
My experience with this build: Since I didn't install GApps, I didn't reproduce the chronic slowdown that @thunder2132 mentioned. Any ideas for fixing audio? Trying to play an MP3 or M4A file in any app hangs the app; pressing the record button in Sound Recorder does not start recording. Also, LOS did not detect the SIM card.
Some notes for others thinking of trying this build: The recovery image linked in the original post is a version of CyanogenMod Recovery, which lacks many of the capabilities of TWRP. (It even failed when I tried to install SuperSU.) However, LOS continued to load successfully after I reflashed TWRP 2.8.5. I also tried installing the Photon Q (asanti) version of TWRP 3.0.2, since that's what TWRP Manager suggests for the XT296, but this TWRP version failed to load for me.
Related thread: https://forum.xda-developers.com/droid-razr-hd/help/xt926-4-1-1-to-lineageos-14-1-t3636103
pentaflox said:
@error28, can you submit your work to a LOS branch so that others can commit changes, too? I retried installing this build today using the recovery you linked. Even though some things don't work, this seems like a great start and it would be terrific if it attracted more contributions.
My experience with this build: Since I didn't install GApps, I didn't reproduce the chronic slowdown that @thunder2132 mentioned. Any ideas for fixing audio? Trying to play an MP3 or M4A file in any app hangs the app; pressing the record button in Sound Recorder does not start recording. Also, LOS did not detect the SIM card.
Some notes for others thinking of trying this build: The recovery image linked in the original post is a version of CyanogenMod Recovery, which lacks many of the capabilities of TWRP. (It even failed when I tried to install SuperSU.) However, LOS continued to load successfully after I reflashed TWRP 2.8.5. I also tried installing the Photon Q (asanti) version of TWRP 3.0.2, since that's what TWRP Manager suggests for the XT296, but this TWRP version failed to load for me.
Related thread: https://forum.xda-developers.com/droid-razr-hd/help/xt926-4-1-1-to-lineageos-14-1-t3636103
Click to expand...
Click to collapse
Maybe someone will try one of this two ROM´S -> https://forum.xda-developers.com/dr...resurrectionremix-nougat-xt907-xt905-t3697567
-> https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
And yes it´s for the RazR-M, but it´s mostly the theme...
I have tested both...on my RazR-HD XT925...and can say ...very smooth...stable no big Problems so far...:good:
The only conditions: you must have JBBL and you must format DATA-Partition in F2FS !
WfG Konrat
|Konrat| said:
Maybe someone will try one of this two ROM´S -> https://forum.xda-developers.com/dr...resurrectionremix-nougat-xt907-xt905-t3697567
-> https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
And yes it´s for the RazR-M, but it´s mostly the theme...
I have tested both...on my RazR-HD XT925...and can say ...very smooth...stable no big Problems so far...:good:
The only conditions: you must have JBBL and you must format DATA-Partition in F2FS !
WfG Konrat
Click to expand...
Click to collapse
I'm willing to try this if I can ever get it working. Is there a published method for downgrading the bootloader without reinstalling stock? I assume there's no CDMA support in the XT907 blob.
pentaflox said:
I'm willing to try this if I can ever get it working. Is there a published method for downgrading the bootloader without reinstalling stock? I assume there's no CDMA support in the XT907 blob.
Click to expand...
Click to collapse
I don´t now another method to downgrade...only with install stock...
But i think it´s relative simple...
In the original JB-Rom edit the "XML" and remove the 2 Lines with "partition_signed" and "tz_signed"...
And flash with RSD
Maybe you should then turn on Wlan, GPS, NFC and Bluetooth before flashing the Nougat-Rom...in the past there were problems when flashing with turn off...especially with Wlan....go´s after that never on
Because of CDMA...I don´t now ...must you test...in the build.prob are lines with CDMA config...but i don´t now the meaning...
konrat
error28 said:
What about LineageOS 14.1?
I plan to attempt to build 14.1 next. But unlike 13.0 it doesn't already have an xt926 build target defined so it's going to take some extra work. If all goes well, I'll be able to post builds in the next few days. If not...
Click to expand...
Click to collapse
Have you had the time and opportunity to try a LOS 14.1 build? I am interested in this as I have an XT905 (basically an xt907 with a different radio) and my build for the KKBL for LOS 14.1 does not successfully boot. I think that maybe/possibly when we go to Oreo that only the KKBL version will work.
error28 said:
Why don't you support JBBL?
Because it would be a lot of extra work. And from the preliminary look I've taken, it seems that 14.1 will probably require KKBL anyway, and not work at all with JBBL.
Click to expand...
Click to collapse
FYI: The fact that people are using my JBBL builds for an XT907/XT905 I think proves LOS 14.1 can run on the JBBL. Its actually one of the most stable ROMs I have personally used.
error28 said:
Does it work on xt907/xt925?
It should do. I don't have either of these devices so I can't test it and I can't guarantee it. But you can always try it!
Click to expand...
Click to collapse
Can someone document the steps they take to convert an XT907 ROM to that of an XT925/XT926?
error28 said:
Recovery: lineage-13.0-20170706-UNOFFICIAL-xt926-recovery.img
Click to expand...
Click to collapse
If someone documents the conversion of an XT907 ROM, maybe I could try and compile TWRP 3.1.1 for the xt925/xt926. Maybe.
error28 said:
Instructions:
Flash recovery from fastboot (optional). You can use the included recovery or some other recovery you already have.
Flash system ZIP from recovery. Flash gapps at the same time before rebooting out of recovery.
Wipe data/cache.
Reboot system and Enjoy!
Click to expand...
Click to collapse
thunder2132 said:
I've had this issue in the past. First wipe your system, I usually do a format data as well (you will lose everything on your internal SD if you do this, external SD should be fine). Install CM 11, reboot to recovery, don't wipe and dirty flash whatever CM/LOS rom you want.
Click to expand...
Click to collapse
FYI: Although its a different phone with a different Kernel, for the XT907 JBBL Nougat ROM's (not Marshmallow) we also had to reformat the Data partition as F2FS.
pentaflox said:
can you submit your work to a LOS branch so that others can commit changes, too? I retried installing this build today using the recovery you linked. Even though some things don't work, this seems like a great start and it would be terrific if it attracted more contributions.
Click to expand...
Click to collapse
And thats the problem, contributors for our aging phones are hard to find, and extending beyond your own computer takes extra work & time. I know I have not placed my work onto GITHUB. I built personally just to get Nougat ResurrectionRemix for me personally, not for the betterment of the world
pentaflox said:
My experience with this build: Since I didn't install GApps, I didn't reproduce the chronic slowdown that thunder2132 mentioned. Any ideas for fixing audio? Trying to play an MP3 or M4A file in any app hangs the app; pressing the record button in Sound Recorder does not start recording. Also, LOS did not detect the SIM card.
Click to expand...
Click to collapse
Have you tried taking a Logcat and lookiung at the results? or maybe even posting them on www.hastebin.com in case someone is interested enough to look for you?
pentaflox said:
Some notes for others thinking of trying this build: The recovery image linked in the original post is a version of CyanogenMod Recovery, which lacks many of the capabilities of TWRP. (It even failed when I tried to install SuperSU.) However, LOS continued to load successfully after I reflashed TWRP 2.8.5. I also tried installing the Photon Q (asanti) version of TWRP 3.0.2, since that's what TWRP Manager suggests for the XT296, but this TWRP version failed to load for me.
Click to expand...
Click to collapse
My brief look at the source code shows that the xt897 and the XT925/XT926 use different touch/display drivers.
---------- Post added at 10:43 AM ---------- Previous post was at 10:42 AM ----------
|Konrat| said:
Maybe someone will try one of this two ROM´S -> https://forum.xda-developers.com/dr...resurrectionremix-nougat-xt907-xt905-t3697567
-> https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
And yes it´s for the RazR-M, but it´s mostly the theme...
I have tested both...on my RazR-HD XT925...and can say ...very smooth...stable no big Problems so far...:good:
The only conditions: you must have JBBL and you must format DATA-Partition in F2FS !
Click to expand...
Click to collapse
Again, any chance you could document what you change to get it to run?
pentaflox said:
I'm willing to try this if I can ever get it working. Is there a published method for downgrading the bootloader without reinstalling stock? I assume there's no CDMA support in the XT907 blob.
Click to expand...
Click to collapse
|Konrat| said:
I don´t now another method to downgrade...only with install stock...
But i think it´s relative simple...
In the original JB-Rom edit the "XML" and remove the 2 Lines with "partition_signed" and "tz_signed"...
And flash with RSD
Maybe you should then turn on Wlan, GPS, NFC and Bluetooth before flashing the Nougat-Rom...in the past there were problems when flashing with turn off
Click to expand...
Click to collapse
I personally never use RSD, I explicitly use fastboot to manually upgrade/downgrade my bootloader and recovery etc. The below is expoicitly for an xt905, but should be pretty easy to convert for your device
Code:
mfastboot flash partition "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\partition_signed"
mfastboot flash sbl1 "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\sbl1_signed"
mfastboot flash sbl2 "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\sbl2_signed"
mfastboot flash sbl3 "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\sbl3_signed"
mfastboot flash rpm "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\rpm_signed"
mfastboot flash tz "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\tz_signed"
mfastboot flash aboot "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\aboot_signed"
mfastboot reboot-bootloader
mfastboot flash modem "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\modem_signed"
mfastboot flash fsg "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\fsg_signed"
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash logo "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\logo"
mfastboot flash devtree "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\devtree_signed"
mfastboot flash boot "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\boot_signed"
mfastboot flash recovery "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\recovery_signed"
mfastboot flash system "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\system_signed"
mfastboot flash cdrom "H:\My Documents\MobilePhone\2014 Motorolla XT905\RSD_IMAGES\JB\XT905 RETAIL Firmware\cdrom_signed"
mfastboot erase tombstones
mfastboot erase userdata
mfastboot erase cache
mfastboot reboot-recovery
Your partitions may be different, and your files and locations will definitely! be different
|Konrat| said:
Because of CDMA...I don´t now ...must you test...in the build.prob are lines with CDMA config...but i don´t now the meaning...
Click to expand...
Click to collapse
Yeah, hmmm.. we dont have CDMA in Aus either, so I didnt test it. However, I did not remove any explicit CDMA code, but did change the "labelling" of CDMA stuff to remove company names/branding, so maybe that would of broke something
Again, any chance you could document what you change to get it to run?
Click to expand...
Click to collapse
I have nothing changed.
I was on kitkat and flashback to JB with an "JB-O2DE-ROM"..."O2" Is an Provider in Germany
(changed before the xml).
And flash with RSD-light.(it´s btw. only a Gui for Fastboot)
Than i flash your TWRP with Fastboot and than wiped all and reformat DATA and CACHE Partition to F2FS
After that i flash your ROM and Open GApps...booting...
Than i tweak a little bit the build.prob...Display Density to 320... Model Name...Country Code
And Viola... ready
WfG Konrat
|Konrat| said:
I have nothing changed.
I was on kitkat and flashback to JB with an "JB-O2DE-ROM"..."O2" Is an Provider in Germany
(changed before the xml).
And flash with RSD-light.(it´s btw. only a Gui for Fastboot)
Than i flash your TWRP with Fastboot and than wiped all and reformat DATA and CACHE Partition to F2FS
After that i flash your ROM and Open GApps...booting...
Than i tweak a little bit the build.prob...Display Density to 320... Model Name...Country Code
Click to expand...
Click to collapse
I am suprised that TWRP works, as there is explicit code for the screen resolution. The xt907 being 540x960 while yours is 720x1280
As for the ROM, the zip file explicitly checks for specific model no's. Admittedly I do have a couple in there I wasn't too sure of, but I wouldn't of expected them to have worked on your phone.
From whaqt you are saying above, there is no definitive need to actually compile a ROM or TWRP if you stay on JBBL. Its only maybe a KKBL ROM that is "missing"? as the KKBL TWRP works as-is.
PS: No-one as yet has actually given me a good reason to upgrade to KKBL. The only reason I have heard is that it removes the random flash of
the screen when turning on.
Thanks for the help, @DiamondJohn. I still don't know how anyone is cross-flashing these images—modifying build.prop doesn't seem to be enough. Although I haven't gotten the XT907 builds to work, at least now I've had the experience reverting to JBBL and restoring KKBL, and I've learned a lot more about AOSP. I'm running Mokee OS 5.1 at the moment.
pentaflox said:
Thanks for the help, @DiamondJohn. I still don't know how anyone is cross-flashing these images—modifying build.prop doesn't seem to be enough. Although I haven't gotten the XT907 builds to work, at least now I've had the experience reverting to JBBL and restoring KKBL, and I've learned a lot more about AOSP. I'm running Mokee OS 5.1 at the moment.
Click to expand...
Click to collapse
I would really question @|Konrat|, he appears pretty confident in what he does.
As for simply changing the build.prop, I know there are a number of items that cannot be changed except through the source code at compile time. build.prop mainly does visual things in renaming a device. What is really suprising is that the xt907 has different touch/display drivers
As for 5.1, I personally found Lollipop very problematic on my phone. With random reboots and not being able to run my custom live wallpaper.
DiamondJohn said:
As for 5.1, I personally found Lollipop very problematic on my phone. With random reboots and not being able to run my custom live wallpaper.
Click to expand...
Click to collapse
Thanks for the advice. Did you have those issues with Mokee specifically? It's only been two days but Mokee had serious enough problems that I went back to CM.
pentaflox said:
Thanks for the advice. Did you have those issues with Mokee specifically? It's only been two days but Mokee had serious enough problems that I went back to CM.
Click to expand...
Click to collapse
No, from memory, I used to run BlissPop, Carbon and maybe RR. Mokee seemed too close to CM at the time to really get into it.
---------- Post added at 10:00 AM ---------- Previous post was at 09:55 AM ----------
pentaflox said:
I still don't know how anyone is cross-flashing these images—modifying build.prop doesn't seem to be enough. Although I haven't gotten the XT907 builds to work, at least now I've had the experience reverting to JBBL and restoring KKBL
Click to expand...
Click to collapse
One of the surprises I had with people cross flashing my XT907/XT905 buiulds onto other phones is that the first line of the install script/zip checks that the device is an XT907/XT905, It occurred to me if they flash the XT907 TWRP, then it will probably report itself as an XT907, and thereby pass that test/check.
But I am still surprised that the XT907 TWRP works:silly:
|Konrat| said:
Maybe someone will try one of this two ROM´S -> https://forum.xda-developers.com/dr...resurrectionremix-nougat-xt907-xt905-t3697567
-> https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571
And yes it´s for the RazR-M, but it´s mostly the theme...
I have tested both...on my RazR-HD XT925...and can say ...very smooth...stable no big Problems so far...:good:
The only conditions: you must have JBBL and you must format DATA-Partition in F2FS !
WfG Konrat
Click to expand...
Click to collapse
Can second and confirm this. Both ROM's run great on my RAZR HD MAXX XT926.
RR was too laggy for me personally, it kept rebooting so i decided on crDroid as my daily which so far has been the best ROM i've ever used on this ageing device.
So if anyone is out there still using the RAZR HD as their daily phone give the above a try. They've really given my device a new lease of life and i feel like i'll get another year or two out of it as a result.
Oh and a big thanks for DiamondJohn and the creators behind these ROMs. Thanks!
Aosip for Motorola Z2 Force
What is this?
AOSiP is a quality custom ROM based purely on GOOGLE AOSP source since 6.0 release. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
Obligatory Warning: This guide and ROM assumes you know the fundamentals of fastboot, flashing TWRP, and running a flash all. Your warranty is voided because of the unlocked bootloader. This is a Third Party ROM. Things may not work as expected compared to stock (for better or for worse).
Warning 2: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 3: if you don't flash the firmware so you are on Oreo on both slots, when you boot after flashing, you'll be on Nougat firmware and have a brick. Try a flash all as that's your only hope on recovering your phone.
How to install
1. Download the latest ROM from here.
2. Prepare your phone for AOSP style ROMs. (download one of the firmwares depending on your model)
Flash the firmware with the .bat file. (See links below or on Post #2)
3. Boot to TWRP
4. Flash TWRP to boot image (with the zip from their website.) Reboot to Newly flashed recovery.
5. Erase oem, data, and system
6. Flash rom like you would any aosp rom, in twrp.
7. Reboot to bootloader
8. run the command "fastboot -w" (this will erase EVERYTHING from your phone, even internal SD, but is needed to have these ROMs work)
9. reboot.
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Volte (T-Mobile)
Change quick charge
Fingerprint reader
NFC
Lights
Sound / vibration
Some motomods (soundboost mod doesnt work)
Team Illusion:
Josh Fox (xlxfoxxlx)
Akhil Narang
Sri Harsha (@srisurya95)
Shreesha Murthy
Brett Montague
Known issues
1. WiFi Calling hit and miss
2. Cannot flash Gapps (included temporarily)
3. some Audio recording apps will not have audio recording work (phone functions fine)
4. if you don't fastboot -w, you will not boot.
5. if you don't flash the firmware your bootloader might relock itself and be stuck on Nougat.
6. SElinux is passive (meaning CTS check will always fail until further notice.)
Downloads:
official link(aosiprom.com)
Thanks to everyone at @aosip @mosimchah @moto999999 and @codeworkx for their amazing work
Android OS version: 8.1.0
Security patch level: April 2018
Build author: @Infect_Ed
Source code: https://github.com/AOSiP-Devices/device_motorola_nash - AOSiP source.
https://github.com/InvictrixRom-devices/kernel_motorola_nash - kernel
https://github.com/TheMuppets/proprietary_vendor_motorola - vendor blobs
Contributors
@Infect_Ed @invisiblek @npjohnson @erfanoabdi @joemossjr @jbats @nathanchance
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.4.x
Phone Firmware Required: 8.0
T-Mobile
Sprint
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-03-28
Created 2018-03-28
Last Updated 2018-04-10
Note: I did not build this. If you want to give thanks for this ROM build, thank @Infect_Ed for building AOSiP, I am just maintaining the support thread for XDA.
Firmware files needed!
T-Mobile:27.1
Sprint: Found em!
Sources Post:
https://github.com/AOSiP-Devices/device_motorola_nash - AOSiP source.
https://github.com/InvictrixRom-devices/kernel_motorola_nash - kernel
https://github.com/TheMuppets/proprietary_vendor_motorola - vendor blobs
Bug reports:
If you don't flash the firmware and your other slot is nougat, after flashing the ROM, you'll brick. (Custom ROM with a locked nougat slot.) Your only hope is attempting an official flash all and try again after flashing the firmware zip in the posts above.
Fair warning and off-topic: I am okay with some off topic questions. If you have a question, please use the search function. If I have addressed the question before, I will not answer and advise to find it in the thread. I will report the post for a mod to delete along with my response to keep the thread tidy. It seems some users think this ROM has international support. It doesn't and won't unless someone with another variant or an unlocked T-Mobile/Sprint model tests, confirms and debugs for that international carrier. Please keep in mind of what I said below regarding this. I posted this on page 20 or so and copying here for better visibility.
Your SIM is locked. You are trying to run a phone off it's intended network. Please don't post those problems here. It isn't ROM related. Like the thread states. It works for T-Mobile and Sprint only on their respective models on their locked networks. Any other tom foolery isn't supported and must be kept out of the thread. After this it will be considered off topic.
Edit: if you have Sprint or T-Mobile service and run into issues with using your (albeit, expensive) international roaming plan, I will assist with that if it works on stock but not AOSP. If you don't have a sprint or T-Mobile sim, I cannot help. Almost all devs on this device won't be able to help. "Almost" all of us are on US carriers.
Click to expand...
Click to collapse
Images posted here
@Uzephi is your device on sprint? Data works but LTE does not? Does the Moto Mods support Hot Swapping? This is great progress and can't wait to see more on this phone.
xDABZx said:
@Uzephi is your device on sprint? Data works but LTE does not? Does the Moto Mods support Hot Swapping? This is great progress and can't wait to see more on this phone.
Click to expand...
Click to collapse
Motomods work with kernel in ROM (hot swapping should as well iirc, I don't use the mods that often where my projector is outdated) LTE doesn't work on Sprint, but 3G and 1xTT works fine.
@Uzephi if we were to flash your kernel, we would lose motomods support?
cervantesjc said:
@Uzephi if we were to flash your kernel, we would lose motomods support?
Click to expand...
Click to collapse
For now, yes. Still trying to get it work. Clang is being a PITA on my build box, having to go to Linaro which can't build the Motorola Greybus driver correctly.
Thanks sir, I appreciate what you've done for the community, finally can go back to my moto from a GS8+
I'm sorry if this is a dumb question but...
Ive never had to install different firmware before on a ROM. If I install this, will it change the process of installing a different ROM in the future?
Thank you.
Sprint varient if it matters by the way.
Edit: I'm sorry for this but is there a way to do this without the .bat file? currently working on OSX
wcain89 said:
I'm sorry if this is a dumb question but...
Ive never had to install different firmware before on a ROM. If I install this, will it change the process of installing a different ROM in the future?
Thank you.
Sprint varient if it matters by the way.
Edit: I'm sorry for this but is there a way to do this without the .bat file? currently working on OSX
Click to expand...
Click to collapse
Open the bat file in a text editor and run each of those commands one by one.
This I'd a dual boot device. Your other slot has the older Nougat bootloader. That firmware flashed the current Oreo firmware to both slots. If you don't do that, and you flash one of these ROMs, you'll reboot to your nougat slot, locked and pretty much screwed without a flash all and luck of being able to flash OEM images in oem mode.
Edit: you won't need to flash this any consecutive times until there is another big firmware update like nougat to Oreo was.
Uzephi said:
Open the bat file in a text editor and run each of those commands one by one.
This I'd a dual boot device. Your other slot has the older Nougat bootloader. That firmware flashed the current Oreo firmware to both slots. If you don't do that, and you flash one of these ROMs, you'll reboot to your nougat slot, locked and pretty much screwed without a flash all and luck of being able to flash OEM images in oem mode.
Edit: you won't need to flash this any consecutive times until there is another big firmware update like nougat to Oreo was.
Click to expand...
Click to collapse
Thank you for the quick reply. I've installed the firmware, but now when I boot to TWRP and try to install the ROM, it instantly fails with ERROR:1. Tried redownloading with a different browser but got the same result. I feel like I'm missing something obvious.
wcain89 said:
Thank you for the quick reply. I've installed the firmware, but now when I boot to TWRP and try to install the ROM, it instantly fails with ERROR:1. Tried redownloading with a different browser but got the same result. I feel like I'm missing something obvious.
Click to expand...
Click to collapse
Flash twrp zip to your phone, reboot to your phone's newly flashed twrp recovery and flash the rom. If I remember right,you need to wipe oem and system before flashing the ROM as well. I'll add that shortly.
Up and running! Thank you!! Still looking around but I do see a built in updater. Will this function 100%? By that I mean, when the Sprint LTE issue is resolved and whatever else is coming will be handled by the updater?
Thanks again very excited to play around.
wcain89 said:
Up and running! Thank you!! Still looking around but I do see a built in updater. Will this function 100%? By that I mean, when the Sprint LTE issue is resolved and whatever else is coming will be handled by the updater?
Thanks again very excited to play around.
Click to expand...
Click to collapse
Yes, since it's official, it checks the link in OP for any new updates.
For anyone using the ROM, are you seeing notification dots, I tried to get them to work, but they're not working for me.
cervantesjc said:
For anyone using the ROM, are you seeing notification dots, I tried to get them to work, but they're not working for me.
Click to expand...
Click to collapse
Working fine for me thru Evie Launcher. Soundboost mod is broken though. My SoundBoost is recognized and the notification says the mod is attached, but the volume steps are reduced to on/off and no sound comes out.
Edited to reflect that only the sound boost mod isn't working AFAIK.
wcain89 said:
Working fine for me thru Evie Launcher. Mods are broken though. My SoundBoost is recognized and the notification says the mod is attached, but the volume steps are reduced to on/off and no sound comes out.
Click to expand...
Click to collapse
Oh, @npjohnson and @invisiblek don't have the sound mod, so they can't get it to work. All of us in the development discord are trying to mail one out, they can't guarantee when it would get fixed.
Edit: added disclaimer to OP. We can only guarantee what we have works. Like when I do my kernel, the only mod I have is the free projector, so that's the only mod I can guarantee works when I do get it working.
I have an extra soundboost I could mail to someone.
I like the idea of running lineageOS 15.1. I have flashed many 3rd party firmwares via twrp and I had confidence that I could always fix a non-bootable device by flashing back to stock or last known good image via twrp. Since it seems firmwares are harder to come by at the moment, at least pre-built firmwares ready to flash...I am hesitant to guinea pig my phone into unknown territory without a clear path of return. Would someone that has more experience flashing and fixing things when they go wrong feel up to try this?
I don't have any issues running adb or fastboot commands if this is a workable upgrade path, nor do I care if this breaks the camera button or fm radio. Assuming we aren't getting a native lineageOS build anytime soon, I'm interested in the generic treble version.
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
https://www.xda-developers.com/lineageos-15-1-resurrection-remix-available-project-treble/
best i got was aosp boot animation after flashing sony aosp and treble system.img afterwards
I would not do this you may get bricked.
Sent from my LEX727 using xda premium
Just tested. Did not work
thanks for the interest. As I understood the treble builds were supposed to work with treble enabled devices...not sure why it wouldn't be straightforward.
because fancy init scripts in ramdisk maybe
Hi folks! I humbly ask for your help after hours and hours of DIY attempts. I rooted a Z5 Compact a few years ago and, mistakenly, expected this to be similar: I didn't read instructions carefully. Admitting to noob mistakes now.
I followed this:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
with this option:
https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711
I went with the G8441_47.1.A.8.49_CE1.rar firmware, as it seems most compatible. THANK YOU j4nn! Marvelous and relatively simple procedure . Flashed with newflasher (Flashtool doesn't work with XZ1 Compact?).
Rooting worked, but when the phone is on battery it never goes above 20%. It was 100% before and 20% immediately after flashing. Red warning light is on, unless the phone is off and plugged in.
So. I missed the part about omitting persist* and Qnovo*. Somehow my attest keys didn't break (PROVISIONED in service test).
It looks like what happened is I replaced the battery config? Info:
https://forum.xda-developers.com/xperia-x/help/flashed-xperia-x-low-battery-t3441158
https://forum.xda-developers.com/xperia-xa/help/strange-battery-issue-jumping-33-3-0-t3688178
Can't repair with Xperia Companion because unlocked bootloader (no way it could be re-locked, is there? My DRM keys are backed up).
Someone wrote about wiping the Qnovo partition. Any advice on how to do this? fastboot format Qnovo didn't work (looks like it doesn't find that partition)
Unrelated, and sorry if this is a total n00b question, but where on earth is TWRP compatible with this device/FW? j4nn's rooted kernel doesn't play well with TWRP install, so I'm hoping to just fastboot boot recovery.img. I can't find any recovery.img that works - I tried several of these:
https://androidfilehost.com/?w=files&flid=232371
But it just gets stuck on SONY logo, needing soft reset.
ben_pcc said:
Hi folks! I humbly ask for your help after hours and hours of DIY attempts. I rooted a Z5 Compact a few years ago and, mistakenly, expected this to be similar: I didn't read instructions carefully. Admitting to noob mistakes now.
Click to expand...
Click to collapse
Try this - https://developer.sony.com/develop/open-devices/get-started/flash-tool and report back.
WORKED. Flashed the US firmware with "Software Update Content Erase", battery now seems to be working normal again. Thank you so much!
Another question: I'd love to set this phone up to work with fastbooting TWRP (so, not a TWRP install on the phone). Is that possible with 47.1.A.8.49? If not, advice on what firmware to use that'll allow rooting per j4nn's methods? Preferably compatible with https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711
ben_pcc said:
Is that possible with 47.1.A.8.49? If not, advice on what firmware to use that'll allow rooting per j4nn's methods?[/url]
Click to expand...
Click to collapse
Why use such old FW? If you're sticking with Oreo then you want the FW ending .20 for the latest. An unlocked bootloader is all that required to boot TWRP from fastboot on any FW.
Because I didn't know better. Emma gave me 47.1.A.16.20, I'll stick to that
Would you mind sharing what *img file exactly would work with fastboot that way? I had no trouble finding it for the Z5 compact, but one that would work here is eluding me. For example, if I run:
fastboot boot twrp-3.2.3-0-lilac-1.img
The phone boots up to SONY logo (black on white background) and stays there, unresponsive. Got the file from https://androidfilehost.com/?w=files&flid=286271
ben_pcc said:
Would you mind sharing what *img file exactly would work with fastboot that way?
Click to expand...
Click to collapse
Have you missed this post, which is linked to in the threads you've posted links to? - https://forum.xda-developers.com/showpost.php?p=79880858&postcount=1029
I missed it but I also miss how that would help. I read the whole thing, and this stands out: fastboot boot twrp.img
I've done that with my old phone (Z5 Compact). I can't find a usable twrp.img anywhere. I fear like I'm missing something obvious
ben_pcc said:
I missed it but I also miss how that would help. I read the whole thing, and this stands out: fastboot boot twrp.img
I've done that with my old phone (Z5 Compact). I can't find a usable twrp.img anywhere. I fear like I'm missing something obvious
Click to expand...
Click to collapse
From the last page - https://forum.xda-developers.com/showpost.php?p=83844543&postcount=1657
Although I would simply install the latest and use one of the unrooted kernels then root it with Magisk.
Hmm. I was aware of that. I tried several of the twrp*.img files, they all get stuck booting on the SONY logo.
Are you sure this is true:
An unlocked bootloader is all that required to boot TWRP from fastboot on any FW.
Click to expand...
Click to collapse
I'm wondering if a FW update would solve the TWRP booting problem.
I've setup this phone a bit at this point and flashing a new firmware (erasing everything) would be painful. Is there a way to safely do a firmware update on a rooted device? Emma offers 47.2.A.*, but only for UK ROMS. I'd installed the 47.1.A.16.20 US ROM.
ben_pcc said:
Are you sure this is true:
Click to expand...
Click to collapse
I know it used to be. Done a bit more searching for you https://forum.xda-developers.com/search/thread/3706704?query=fastboot twrp, and found this command...
Code:
fastboot reboot bootloader
fastboot boot twrp-3.3.1-0-lilac-pie-5.img
...I've just tried it, in fastboot mode and it booted TWRP.
ben_pcc said:
I've setup this phone a bit at this point and flashing a new firmware (erasing everything) would be painful. Is there a way to safely do a firmware update on a rooted device? Emma offers 47.2.A.*, but only for UK ROMS. I'd installed the 47.1.A.16.20 US ROM.
Click to expand...
Click to collapse
Starting over is always painful but sometimes it's the best option. I have a rooted stock ROM and TWRP installed with no issues, on Oreo or PIE so if you do, then I suggest backing up the essentials and starting again.
YES. Thanks so much SXUsr! You were right after all, I tried a few different TWRP images and they work now. What I was missing was fastboot reboot bootloader. My Z5 Compact doesn't require it.
There was one more thing I had to figure out: data partition is encrypted, and for my (Android 8.0.0) device the TWRP you mentioned fails.
twrp-3.2.3-0-lilac-1.img on the other hand asks for my unlock pattern when it boots up, and backs up fine.
Now that I have a complete backup I'll consider my next steps (possibly flashing a new ROM. Honestly 8.0.0 seems fine, we'll see). Thanks again!!
ben_pcc said:
YES. Thanks so much SXUsr!
Click to expand...
Click to collapse
You're welcome. I've always installed it on this phone so wasn't aware of that command myself either, so we've both learnt something.